🚀 Deployed on https://5e9af2ed8d1bfb211343aa2b--nixos-homepage.netlify.app

@garbas thanks for the feedback!

Just add a redirect to netlify.toml, since once we merge the change goes public

i made no change to the structure, just the content. but i can add it in this PR

Most likely Bugs should be also part of the Contribution guide, somewhere under Learn page.

Yes, it can be a section in a Contribution guide and we can link it from Learn page as "Report Bugs".

Documentation (Documentation page)

You probably ment Learn page

i mean any documentation page that fits. it's mostly links to NixOS manual, so learn might already cover it.

🚀 Deployed on https://5e9e0b418de5a2a87b1e7ee8--nixos-homepage.netlify.app

🚀 Deployed on https://5e9e0d6738ac70a5f27d01b7--nixos-homepage.netlify.app

Just add a redirect to netlify.toml, since once we merge the change goes public and it makes no sense to put it in a separate PR.

I git mv nixos/community.tt community.tt and committed it to the same commit as the changes, but now it's saved as delete/create instead of rename and the actual changes to the text and page history are lost :(

I wanted to prevent that.

I added it as a second commit, but now i'm unable to edit the first commit.

🚀 Deployed on https://5e9e0f25e08609f41c747af4--nixos-homepage.netlify.app

🚀 Deployed on https://5e9e15978de5a2f4661e8a5a--nixos-homepage.netlify.app

🚀 Deployed on https://5e9e1eddad0b3c01707767ef--nixos-homepage.netlify.app

I really dislike this merge. Nothing against a rework in general and nothing against your rework, davidak.

BUT: The merge was too early. Removing useful informations from the homepage is a bad idea. Now, there isn't a link to the bugtracker anywhere on the homepage, and effectively also no link to the github-repository anywhere! First, a new place should be found on the homepage for this information, and afterwards it can be removed from the current location. Not the other way round!