Any updates? How’s the progress?
I have improved the score of SEO but I cannot get it to 100 because Lighthouse does not like the word “here” for links. If we want to get 100 score, albeit probably unnecessary, we need to change the word.
“Here are a few reasons users love Anki” → “Learn why people love Anki”
- We’re avoiding “here”.
- We’re also replacing “users” with “people” which is a less dry and a broad wider term.
What does everyone think? Can you use this and check the metrics again, ittipat?
Sorry for not being clear, the “here” that I mean is using the word as <a>
tags. I have updated the text as follow to acheive 100 score.
Installation guides can be found here → Here are the installation guides
the reasoning can be found here → here are the reasons
However, I also support the change to “Learn why people love Anki” because there are two “here” already on the website.
The note regarding Qt6 being recommended is outdated. The Qt5 build had been dropped due to various breakages, which means it cannot be downloaded anymore and the manual doesn’t mention it anymore. Thus, in my opinion, the explicit mention of “Qt6” should be dropped, since most users won’t know what that means anyways.
I think if somethings states “Here are…”, the link should be at the word “here”, because the focus is on where to find it, not what you find there. E.g.
“Here are the installation guides.”
Having “installation guide” as a link only makes sense in my opinion if you have something like the following:
“Please see the installation guide for further assistance.”
I’ll explain why this is bad. If you’re using a screen reader (visually impaired or otherwise) one of the ways you can skim through a website is jumping from one link text to another. (There are also other ways screen reader users do this).
It provides a very bad experience when you’re not a normal vision person and are trying to quickly find something and every link you jump to says “here”. That’s why we prefer meaningful link text over vague words like “here”.
Well, I think I read Nngroup’s research stating even normal vision people notice link text more so there’s that too.
I agree that having a link in “Here” might be bad. I had no idea about possible issues with screen readers though, so that’s good to know.
I wasn’t super clear yesterday. What I meant is having a sentence with “Here” (but “here” not being a link) doesn’t make much sense to me, which is why I’d propose a rephrase that makes more sense to me, like this:
But not quite sure how to explain it better. “Here” is directing the user to a certain place, whereas my example sentence above focuses on what you’ll see when you open the link (focus isn’t on the “where” but on the “what”).
I understand the current site is only a template though.
That I agree with you. “Learn more…”, “For details, see…” are better phrasings.
I have updated to “For details, see installation guides“. (waiting for merging)
Are you waiting for some action on my part? If it’s already ready to go, I can look into cloning the repo and getting the domains set up.
Sorry for the confusion, I was not waiting for anyone’s action. I just wanted to provide update on the progress. I was referring to the pull requests on the Toby’s repository. However, if Toby wants me to handle the rest, I am willing to do it.
Thanks for everyone’s patience. I’ve reviewed some of the requested changes. @dae would you like us to begin the process of transferring the repository to the ankitects organisation? I think any GitHub actions and deployment changes should occur once the repository has been transferred
I have an up-to-date copy of the repo at GitHub - ankitects/anki-landing-page, but it looks like no GitHub actions have been added yet? Are you suggesting they be added via a PR to that repo?
I have moved my pull requests including GitHub actions to GitHub - ankitects/anki-landing-page.
The landing page is now live at Anki - powerful, intelligent flashcards
Are there any last-minute changes people want to see? If not, I’ll look at switching the old official website over to this.
I resolved the merge conflict in feat: add descriptions to increase SEO score by ittipatken · Pull Request #1 · ankitects/anki-landing-page · GitHub but you also can merge after the website went live.