Hi everyone, here’s yet another the Fedora Website Revamp project design update!
I have an initial first-cut (read: still very much open to change and feedback and ideas) draft of the Fedora Workstation Community page that will reside within the revamped Fedora website. This page will be used as a model to base other Edition download pages from, so even if Workstation isn’t your main concern, your feedback on this mockup will be useful.
This page would be accessed by clicking on the “Community” navbar item in the Fedora Workstation navigation bar:
You can view the full mockup here on Penpot:
Let’s walk through it via snippets of the mockup from top-to-bottom to provide some context.
Some upfront notes:
- The current working thought is that this page would reside at https://fedoraproject.org/workstation/community .
- The content is a combination of Workstation-specific community information (e.g. the Workstation Working group contact and meeting info, and Fedora-wide community information (e.g. events like Flock and the release parties). The Fedora-wide community will be repeated in each edition’s page and project-wide. Ideally this info would come in the form of a component that could just have one content source that could updates all locations it is displayed at, at once.
- It is the intention we would have a dark-mode version of this page and various elements have been designed with that possibility in mind, but I don’t have a complete working version of that mocked up yet.
- Some of the screenshots have grey around the borders because that’s the background color for Penpot… that grey is not intended to be part of the page design.
TOP HEADER AREA
Like the Download page for Workstation, this page header area is a bit lower-key than the splashy front page with the hero image. It may, in fact, be a little too low key. We are looking into creating some illustrations or making the use of photography here to make this section a bit more of an anchor for the page / have some more visual interest.
You should note the intended consistency here between non-front pages of the main Fedora Workstation top-level pages - large header in the edition color or with an edition color accent (here it is green) and a slug explaining what the page is about / what it helps you do.
In the bottom half on the header we have some text explaining which sub-community / team “owns” the edition, basically identifying by name the community for Fedora Workstation right up top. Since the Workstation Working group has its own page at docs.fpo, the link here is intended to point to that.
Again, this section is a bit too low-key, so any ideas on specific imagery to use here would be greatly appreciated 
COMMUNICATION BLOCK
Next we have a block for listing the main communication channels through which this community communicates. I’m imagining the Matrix channel name can be a link to matrix.to to join right away, but not sure what’s the best these days for linking folks to an IRC channel (I used to use chat.freenode.org’s web interface back in the days freenode still existed.) Any ideas quite welcome Anyhow I’m thinking the action button should point to Matrix as well.
The mailing list link & action button will point to the Hyperkitty archives page.
The forum action button will point to the workstation tag here in this forum
GET INVOLVED BLOCK
The “Get involved” block basically has a couple of concrete things you can do to get involved in this community - report/discuss issues, and attend a meeting. If you can think of any other things we could list here or better suggestions than these, we are all ears
EVENTS BLOCK
Our events are an important part of our community. This block will probably be repeated verbatim across the different editions. However, it would be nice if possible to customize it by having a link to a past talk that is relevant to the edition at hand. You can see under Colúr there is a screenshot of a presentation from last year’s Flock - something like this related to the edition would be quite nice.
The best information about our events is seasonal - after Flock, we want to see the recordings of the talks that just happened. Leading up to Flock, we want to solicit proposals. Getting closer, we want folks to register and take a look at the schedule and plan what to attend. And during Flock we really want to highlight and drum up attendance to talks on the schedule. If it is at all possible to do this here, obviously that would be ideal, but a low-maintenance alternative is to update it with a link to a relevant talk… or event better, a playlist of talks related to the edition at hand (here, Workstation.)
This layout emphasizes Flock as an “umbrella” brand over the two events we are running in these COVID times: nest, our at-home virtual Flock, and hatch, our in-person microconferences all over the world preceding Flock nest.
We also will highlight release parties as seen here. Again, these are seasonal. Whatever is the next upcoming event we should have more details about.
At the bottom of the mockup above you can see one of our contextual “on ramp” prompts - suggesting that a good way to contribute to Fedora would be to attend and propose a talk
We have a Colúr block here that shows the “Call for proposals” mode for Flock. I have two other modes mocked up - register mode, and post-event recordings mode:
Again, these are kind of blue sky, “wouldn’t it be really nice” if we could make these seasonal. If not, we could default to just linking to the Flock site and handling this all there alone.
MEDIA BLOCK
Next, we have a media block - letting would-be new community members know where to keep up with what is going on in the community, and pointing out the differences between the Fedora Community Blog and Fedora Magazine.
There’s another contextual on-ramp: hey, you could write an article for one of these publications or help us come up with proposals and edit the content 
FOOTER
This is just the standard footer:
FEEDBACK WELCOME!
So here you have a little update on how things are going for the Community section of the Workstation page design. My next step besides sharing this with you here and evaluating your feedback and rolling it back into this to iterate and improve it
Looking forward to hearing your thoughts on this!