I mostly agree with Expertium but also think we should complete the basic page first. Then maybe we can move the “Contributing” etc. to a different page.
I will just mention one other thing that I have noticed: you are using British spellings for words like “synchronisation” which I personally like but in Anki we generally write “synchronization” and “optimization”.
I’m not even going to weigh in on this - I think we should hold off on any further bikeshedding until this in a public repo with issues and PRs.
In my opinion there is nothing wrong with free discussion, the OP’s landingspageguage created this thread for the purpose of hearing some thoughts, and for free volunteers chatting is important because it is a meaning to participate in community activities.
My fear is that progress will get bogged down due to all the well-meaning suggestions, and the OP may end up burning out before this even gets to a state where other people can pick it up and continue working on it.
Some progress for those interested. I’m going to exclude the hero graphic for now, this can be introduced at a later date. I intend to have this available for review by the end of this week, with the following task completed prior to publishing for a review:
I didn’t end up having enough time to implement the hamburger menu navigation, but I don’t want this to delay initial feedback. I won’t be available to work on this for another week now but I think this is non-blocking to gather the first round of feedback.
good job bro
i want to give some notes , maybe some devs will work on it
light mode needed
gonna be better if you add a direct link to add ons page in the main page (which
is absent in the current version)
some illustrations gonna make it more beautiful and give it some aesthetic vibes (like Ebbinghaus graph or the fsrs graphs etc)
better if you use the anki logo that it’s used on ankiweb (2D)
you did really a good job , thank you for the effort
Thanks Toby, I’ll take a look at this next week.
I think we should get a new favicon for the site now. The current one looks something like this on my device:
For some perspective, this is what server and subreddit are using:
dae’s profile picture looks much better than the site favicon. Seems dae has his priorities straight /j
My apologies for the long delay here; this got lost among the rest of my backlog. Thank you for being so patient! I’ve finally found some time to review the site, and I think it’s looking great.
Some minor issues I noticed:
Some of these others happen only when the custom font is removed.
The learn more button wraps onto two lines. (font)
Testimonials: arrows should be a little lower from the text (font)
Contributing boxes: remove blank space in middle / make more rectangular?
‘can be found here’ missing trailing period
Hamburger menu feels a little unnecessary. If we are to link to add-ons
on that page (and personally, I don’t think it’s necessary, but I know some
disagree), perhaps the link could be moved elsewhere (e.g. contributing
section).
The final step would be a GitHub workflow that runs on push/merge, and automatically builds the website and makes it available in a subfolder. We can then configure GitHub to point https://apps.ankiweb.net to the GH docs, and then webpage updates can be done via PRs instead of the manual publishing I’m doing currently. Bonus points if we can speed up the build by caching node_modules!
Similar setup for our manual:
How about preloading the font? As documented here, it may fix the page redraw.
It might help, but it also slows down the initial page load, and I just am not sure a marginally prettier font is worth it. But then, I am not a designer. 
I would be very reluctant to lose the font, it gives quite a lot of character. May I ask how you viewed the site? I’ve not experience these problems when previewing with the provided make preview . I did forget to preload however so I’ll see about implementing this when I can.
‘make preview’, then refreshing with caching disabled in the network tab of the inspector emulates the first-load experience. I set the network to ‘slow 4G’ to make it more visible.
I would say the font change is worth the loading difference, even on a slow network. Gives the website a professional feeling.
I’ve taken the time to optimise the font loading and also optimised the static images, here’s how a lighthouse test looks. SEO score is low only because I hadn’t bothered with it for now, I could just copy whatever was on the original site but it’s not that important now as it can always be added later by someone who knows what they’re doing.
I will have a look into sorting out the workflow and other minor fixes soon.
How accessible is that font? The x-height, aperture seems a issue to me.
Do you have metrics to support this? I believe this font is more accessible than most, it’s quite similar to Lexend which is scientifically proven to have improved readability. If you could provide fonts with a similar look and feel that are more accessible I’m happy to consider them.
Is there any possibility that the new website will be released at the same time as 24.11? Other than the decision of using a font or not, deploying GitHub pages should be the last thing to do? Static site generation • Docs • Svelte
