Skip to content
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

Website SEO+UX+Content Design issues #120

Open
neozenith opened this issue May 19, 2024 · 0 comments
Open

Website SEO+UX+Content Design issues #120

neozenith opened this issue May 19, 2024 · 0 comments

Comments

@neozenith
Copy link
Member

Thanks to Sophie Benjamin for her UX/Content Design feedback:

Popping my UX/Content Designer head in here to see if anyone is interested in feedback on the site from that lens?

All right, here goes!

Content/text

  • We don’t tell people what Newwie is. Is it a Slack group? Is it a meet up? Is it networking? We do all of these things but we need to call it out. Maybe we’re not clear internally about what Newwwie is. We need to call this out on the home and About pages. This is also important for SEO - the SEO here isn’t great which makes it hard for people to find us using search
  • Every instance of “get an invite” should be replaced with “Join the Slack group” or “Get a Slack invite”. This accurately sets expectations on what sort of “invite” we’re taking about, and what will happen next
  • It’s not the most intuitive design - there’s no hamburger menu or other kind of drop-down to help the user navigate around beyond the links in the footer
  • There are grammar and syntax errors. These make the text harder to understand and makes us look less authoritative and professional as a collective.
  • Is all the info we collect on the Slack invite form necessary? If it is, all good. If it’s not, clearly indicate the optional info or ideally don’t ask for it at all
  • This is what comes up when you google Newwwie - it says we’re a computer club?! This also shows why it’s important we have a paragraph spiel explaining what Newwwie is

Maybe this issue could be split into smaller issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant