-
Notifications
You must be signed in to change notification settings - Fork 255
Redesign Community Page #1195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Redesign Community Page #1195
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This top section looks great, but I wonder if there's something we can do to make the bottom two images appear clickable. Currently, there's not really any visual cue that tells me they are links, other than when I hover them, but that's not available on mobile.
Not sure how... overlay a link arrow over the images? Or an arrow next to the card titles?
To be consistent, I think we want to end the section subtitles with a ., e.g. here:
The community's official channel for answering questions and discussing the development of Swift. ←
For the "Contribute to Swift" section, maybe we can change the subtitle a bit, e.g. to:
Swift welcomes contributions from everyone, whether you write code or help in other ways.
Many of the card descriptions are truncated. We should try to tweak them to be a bit shorter maybe to not truncate for more viewport widths.
I also noticed that some are still WIP descriptions, e.g.: Topics related to the Swift Evolution Process. Another line here.
Mentioning this here as it wasn't called out in the PR description to be missing.
It should be possible to compress the images. I tried one of them and managed to reduce the file size by 75% using a lossless compression.
|
What is the vision for linking to things like Server, C++ interop and other workgroups? It seems we lost those pieces in the current redesign, or should we perhaps make use of those links. I see in the screenshot that we're seemingly hiding them further deeper into the hierarchy, is that the plan or just an idea? I'm a bit worried we're hiding these topics away deeper, vs. I thought we wanted to surface those use-cases more prominently on the website. Will we surface those "focus areas of swift" elsewhere more prominently, without as much focus on the workgroups, if we're hiding the workgroups like that?
We could add one of them to go to the Server category on the forums perhaps? |
|
@ktoso the idea is that we assemble another set of pages that this would reference that focus on how we "run the project" and laying out all of the various groups - steering groups, workgroups, etc - with links to their charters and related information. That page has some rough initial designs, but it's not yet at the "implement this" stage like the above that Fed's enabling for the broader community page. The loose structure that I anticipate for these additional pages is another top level page that's about the overall "how we manage Swift as a project" with sub-pages for each of the groups - core team, steering groups, & workgroups. |
Motivation:
We need to redesign the Community page swift.org/community
Modifications:
Added new styles, content, assets
Needed:
Result: