Hey guys! Recently I tried to contribute to the nixos homepage and was surprised by the technical architecture and some problems. I cried about it on #nix-offtopic and people said we might need a rewrite.

I collected some thoughts in this document on the matter.

This is by no way a suggestion, a fomal RFC or anything like that, mostly just for sparking discussion and seeing how many people agree.

In reply to @noob_tea:matrix.org

Hey guys! Recently I tried to contribute to the nixos homepage and was surprised by the technical architecture and some problems. I cried about it on #nix-offtopic and people said we might need a rewrite.

I collected some thoughts in this document on the matter.

This is by no way a suggestion, a fomal RFC or anything like that, mostly just for sparking discussion and seeing how many people agree.

That is sort of the plan already, but it is important how we approach this. We all agree on this direction. We are going to proceed in small self contained steps. No big rewrite or heroism or burnout from anybody.

If you wish to help out please join the Marketing team and we can discuss this further. But roughly the plan is:

1. First we need to get our css in order. We agreed on tailwindcss. Minimal changes to html and the website should be needed. As a first goal we should style status.nixos.org and develop basic elements that we can they reuse also on nixos.org (and later search.nixos.org).

2. Only after that we should be looking at the potential generators. mkdocs/hugo/nextjs/.. But before that we need to compile list of requirements that we might need in the years to come.

3. Figure out how to better integrate the docs (manuals/pill/nix.dev/...).

There are many details I've skipped but if you are interested follow here how to join Marketing team -> https://nixos.org/community/teams/marketing.html

In reply to @garbas:matrix.org

That is sort of the plan already, but it is important how we approach this. We all agree on this direction. We are going to proceed in small self contained steps. No big rewrite or heroism or burnout from anybody.

If you wish to help out please join the Marketing team and we can discuss this further. But roughly the plan is:

1. First we need to get our css in order. We agreed on tailwindcss. Minimal changes to html and the website should be needed. As a first goal we should style status.nixos.org and develop basic elements that we can they reuse also on nixos.org (and later search.nixos.org).

2. Only after that we should be looking at the potential generators. mkdocs/hugo/nextjs/.. But before that we need to compile list of requirements that we might need in the years to come.

3. Figure out how to better integrate the docs (manuals/pill/nix.dev/...).

There are many details I've skipped but if you are interested follow here how to join Marketing team -> https://nixos.org/community/teams/marketing.html

hey!

I was not aware this was already in process. I definitely don't want to be the guy randomly appearing and telling everyone they're doing it wrong

a few questions:
What timezone are the metings held in ?
what responsibilities do team members have ?

In reply to @raitobezarius:matrix.org
https://www.docker.com/blog/we-apologize-we-did-a-terrible-job-announcing-the-end-of-docker-free-teams/ oh no