gatsbyjs / gatsby

The best React-based framework with performance, scalability and security built in.
https://www.gatsbyjs.com
MIT License
55.28k stars 10.31k forks source link

[themejam] Design showcase launch and winner announcement state for Theme Jam website #15298

Closed prestonso closed 5 years ago

prestonso commented 5 years ago

Once we are close to or reach 12 contest entries, we need to design the showcase launch state for the Theme Jam website so that improvement of the Gatsby theme can proceed.

Specification

From @jlengstorf:

Showcase launch scope

Once we hit 12 entries (this is a good number because grids flow well at 6/4/3/2 wide) we’ll want to launch the showcase to show contest momentum and boost the visibility of community members who are submitting.

Winner announcement scope

At the end of July, we’ll choose 1–3 winners — at that point we need to update the site to both announce the winners and end the contest.

missmatsuko commented 5 years ago

Would be nice if non-roman characters in screenshots could be fixed for this showcase, and the main one: https://github.com/gatsbyjs/gatsby/issues/5929

fk commented 5 years ago

Here's the first shots at Showcase and FAQ page designs:

Figma prototype / Source

Showcase FAQ

Link to winner showcases

I couldn't figure that one out — plis help @jlengstorf! 🙏

jlengstorf commented 5 years ago

Lookin great so far! A few notes:

  1. I'm pretty sure all the themes are going to be named gatsby-theme-*, so gatsby-theme-blog-purple or gatsby-theme-marvelous — we'll need to figure that out.
  2. How does this work for pagination? I'm not sure we'll have a large enough number of components for a long list to affect performance (I mean, good problems if we get there), but will ~50 entries be too hard to navigate on one page?
  3. Can we see this with real screenshots? I'm a little worried about how the speech bubble triangle will look with actual screenshots.
  4. What are we planning to do for mobile nav? Do we have a standard approach in the Gatsby design system for this?

I'm excited about the FAQ section — we can use CSS :nth-child() to alternate callout styles, which will be doooooope. 🎉

missmatsuko commented 5 years ago

Just noticed the submission form actually asks for a 900x600 screenshot (so 1.5 ratio, and maybe don't need gatsby-transformer-screenshot): https://airtable.com/shrqRYknYY50YCzeq

KyleAMathews commented 5 years ago

Now I want to make a theme called Smithsonian — obviously using the Cooper Hewitt font from https://www.cooperhewitt.org/ :-P 🤔

jlengstorf commented 5 years ago

@missmatsuko good catch! Yes, I actually wanted to avoid the screenshot plugin and let theme authors do a bit of art direction if they wanted. 😄 @fk I should have called that out specifically, sorry.

fk commented 5 years ago

I should have called that out specifically, sorry.

No need to be sorry—I could have noticed that myself! I'll adjust the designs now regarding the screenshot aspect ratio, and add pagination, real screenshots, and a take at the mobile nav (which the design system doesn't have, but will be something hamburger-ish).

fk commented 5 years ago

Updated:

Showcase Showcase (simpler entries)

image

Figma prototype / Source

fk commented 5 years ago

Almost forgot: Updated the item titles to something relatively plausible, chopping the gatsby-theme-* bit away… 🤷‍♂ 😿

jlengstorf commented 5 years ago

This is great, @fk! For the sake of simplicity/maximizing exposure for the theme screenshot, I think the simplified version makes sense.

@gillkyle @amberleyromo any feedback here? If not, I think we're ready to start turning this into code. Kyle, are you able to take the lead on building out the UI? I'll handle the data sourcing for it, so don't worry about that part.

fk commented 5 years ago

Closing for now, lmk if you need anything!

fk commented 5 years ago

Ah hold on, this has "winner announcement state" in the issue title … reopening.

gatsbot[bot] commented 5 years ago

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here.

If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contributefor more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

fk commented 5 years ago

@jlengstorf With https://www.gatsbyjs.org/blog/2019-08-07-theme-jam/ out I think this might be good to close? Or do we need a dedicated page for https://themejam.gatsbyjs.org announcing the winners?

fk commented 5 years ago

Oh just noticed that the "WINNER" label (see designs) seems missing (latest Chrome)—was that intentional?

image

gillkyle commented 5 years ago

Oh woops, the Winner label was a little hacky with a pseudo-selector I think, maybe it just got missed somewhere.