We may need a search feature for contents. :)

The existing FAQ for podmins https://wiki.diasporafoundation.org/FAQ_for_pod_maintainers should be migrated to the new guides system.

Someone needs to go through all the installation guides and test if they actually work.

We currently use the footer to link to frequently visited pages that, for some reason or another, did not fit in the main menu. The footer is WIP anyway, but it really needs some links. :)

The blog posts need to be imported.

The existing FAQ for users https://wiki.diasporafoundation.org/FAQ_for_users should be migrated to the new guides system.

And first, think about what should be included

Currently, all sections have persistent crosslinks in the right header part that direct the readers towards other parts of the site:

The idea is, in principle, good. However, it takes up a lot of space in the header, and reduces the amount of actual navigation items we can place. Also, in some cases, this already breaks for smaller, but not yet mobile, viewports:

I like the large CTA button, but maybe we can rethink this a bit to still have some form of crosslinks available, while not eating up the entire header. Maybe a dropdown-thingy?

Which section does this content belong to?
Upgrade guides, mainly major upgrades.

Request
Make an includeable warning box that alerts podmins to always run migrations inside screen or tmux to avoid their session dying and the migrations being interrupted, as that might yield some bad states.

All the existing contents need to be ported to the new project site.

While the base layout already works, there are several rough edges. For example, take this screenshot:

• headlines are way too big
• header takes up half of the screen.
• date-dividers break as there is not enough horizontal space

And that's just one page, so there is a lot to work on. :)

What needs to be included? How does it look like?

And replace all the wiki links to the updating guide in blog posts

This popped up in a chat on 35c3, but I don't remember who said it. 😿

All contents are markdown files anyway, so we could add a link to GitHub to each site. When on GitHub, the workflow is actually surprisingly simple, clicking the "edit" button automatically creates a fork if you don't have write permissions to the repo, and it's very easy to create a pull request from there.

So far, noone has directly rejected this proposal, so I'll work on it a bit more to polish some things. With people accessing our pre-preview version, it would be good to update the deployed state whenever possible, but I am lazy, so let's autodeploy.

The current site is deployed whenever we push to a production branch, but I feel like this was an unnecessary step. We can develop larger ideas off-master, and be fine with having master autodeploy, so let's do that!

The existing FAQ for web developers https://wiki.diasporafoundation.org/FAQ_for_web_developers should be migrated to the new guides system.

This is a suggestion from @CSammy: We could, in the guided install guide, add a "conclusion" to each of the pages. This would allow people to check if they did everything they were supposed to do.