-
Notifications
You must be signed in to change notification settings - Fork 241
New “Swift is…” and About page copy #336
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
New “Swift is…” and About page copy #336
Conversation
lgtm, I would also consider the option of Swift is a general-purpose programming language approachable for newcomers and powerful in expert hands. It is quick to write, fast to run, modern, and safe. in the "about" page, the "double bolding" seems redundant to me, but not a big deal. |
This looks great, Dave! My only concern is the length of the But as we keep the meta title as "Welcome to Swift.org", this might not be as much of an issue. I'm no SEO expert though. As a side note, maybe we should update that meta title too while we're at it? I think I agree with Tom as well that we don't need the bolding on |
I agree, I like the ending of "quick, fast, modern, and safe". For the about page, I replaced the opening paragraph with the new wording and removed the bolding. |
Yes, I considered this. The most concrete thing I found about how Google would treat this is that it may only pay attention to the first 50-80 characters of what we put in an I'm happy to change it to be a |
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.
👌
<3 |
* Update landing page content (#127) * First pass at the new Getting Started page (#174) * Adding Getting Started tutorial for SwiftUI / iOS 16. (#185) * Add data file with items for "Go Further" section (#184) * Add cli and library getting started guides (#192) * Getting started tweaks (#208) * Rename Markdown files to have an `.md` extension. (#209) * Fix typo (#214) * Update getting started page layout (#204) * Add documentation information to Getting Started (#226) * Add Vapor Getting Started guide (#229) * Update content-improvments branch per feedback (#244) * Tweak SwiftUI tutorial (#240) * Add TSPL Go Further section and resource thumbnails (#227) * Improve 'Why Swift?' section on landing page (#252) * Replace Go Further item for advanced String Under The Hood blog post with item for Structures and Classes chapter in TSPL (#254) * Update landing page layout (#267) * Link to developer.apple.com from apple use case (#291) * Smaller landing page changes on content improvements branch (#294) * Update Go Further section (#300) * Update icons and placeholder image (#301) * Improve description of use cases and getting started guides (#304) * POC: Feature random code snippet on landing page (#303) * New “Swift is…” and About page copy (#336) * Move link to A Swift Tour to the Use Cases section (#329) * Add consistent download section to start and end of each guide (#351) * Add a new install page, update the download page, and move release yml files into one file. (#310) * Update navigation for install page (#355) * Update cli and library getting started guides (#357) * Content improvement guide updates (#373) * Add value and reference types article (#377) * Add some showcase snippets (#371) * Resolve issue with Red Hat download links (#379) * Add Info about Scoop for Windows install page (#382) --------- Co-authored-by: Alexander Sandberg <[email protected]> Co-authored-by: Paul Hudson <[email protected]> Co-authored-by: James Dempsey <[email protected]> Co-authored-by: tomer doron <[email protected]> Co-authored-by: Dave Verwer <[email protected]> Co-authored-by: Tim Condon <[email protected]> Co-authored-by: Max Desiatov <[email protected]> Co-authored-by: Mishal Shah <[email protected]> Co-authored-by: AG <[email protected]> Co-authored-by: Ted Kremenek <[email protected]>
During the last meeting, we discussed having a
h1
with “Safe, Fast, Modern“ above the “Swift is…“ copy here, but after playing with it, I don’t think that feels quite right.I’d be happy to change it if the consensus is to have that strong three-word lead-in, but it didn’t feel quite right to me.
This is what felt best to me:
Then I also tackled the "Safe, Fast, Expressive" section that begins the "About" page as I think they should line up. This copy definitely needs work, this is just a first draft. Let's discuss in this PR.