General Design review

Now that we have actual data in production, we can see that some pages don't really work with the design they have. We need a design review to potentially change fundamentally how some pages display information.

- Global
- Make sure everything is on brand
- General accessibility review: link colours, border colours, layouts without borders, etc
- Navbar
- On very wide screens, the text in the black header looks very off center
- The navbar is quite crowded, which makes responsiveness difficult to handle (the navbar collapses into a hamburger
menu too early)
- Footer
- The footer is pretty but not very practical. Something closer to what element.io does (major titles and links to subsections)
- Front page
- We removed the sponsors page for lack of sponsors in the platinum tier, we will hopefully add it back at some point. We need a proper design for it
- About page
- Doesn't use the black header as the rest of pages
- Need to define what the page is for: Matrix, the Foundation, both? What do other websites and organisations usually do?
- Blog
- Looks very "engineer design"
- The previews are rather large, and difficult to browse
- Blog Post
- The column is off center
- The title sizes are inconsistent (especially in the quotes)
- TWIM posts look very messy
- The ToC has inconsistent link colour (it looks like normal text until you hover it)
- Redesign of the YouTube Player placeholder
- Documentation
- Docs are not searchable (but [could be](https://www.getzola.org/documentation/getting-started/configuration/))
- When scrolling through the docs you don't see in the ToC where you're at
- _Ideally_ having proper styling of the code depending on the language à la starlight
- Ecosystem
- All the subsections are inconsistent
- The cards layout doesn't really work with the density of information we want to display
- It's impossible to navigate back to the parent category when you are looking at a project (#2212)
- Donate & membership
- #2208
- #2184
- Try Matrix
- Do a full review of a user journey to see if it makes sense

Start by reviewing the listed global, navbar, footer, front page, About, Blog, Documentation, Ecosystem, Donate & membership, and Try Matrix areas, along with related issues #2212, #2208, and #2184. Break the broad review into a clearly scoped page or user-journey change; done should mean an agreed design and an implemented, accessible, consistent experience for that scope.

Written by the indexing model from the issue text.