We have an internal doc that we used to describe what type of information should go in each section of our new documentation layout. That doc is now being transferred into the branched called new-docs-layout. I took the next rev, and now it's back to the rest of the team.
@hsanjuan it would be most helpful if you either (or did both of these things):
Kept comments at a relatively high level, ie, how is the content structure looking? Do the categories make sense? and if you see something you aren't happy with, explain why you don't like it as best you can, and/or suggest an alternative so I can understand where you're coming from. Please continue to use the doc for this conversation so it doesn't splinter into 50 different places, and become impossible to track.
Or, please search for TODOs in the files, and do some! They mostly involve doing the re-writing that we suggested in the doc.
Please note: there are lots of things that aren't fixed yet, or even close to fixed (for example, the homepage right now just has a data-dump of paragraphs from other pages -- it's not been made into A Thing yet). It is not helpful right now to point out these very messy bits. It would be best to stay focused on the high-level structure, or diving in and re-writing.
We have an internal doc that we used to describe what type of information should go in each section of our new documentation layout. That doc is now being transferred into the branched called
new-docs-layout. I took the next rev, and now it's back to the rest of the team.@hsanjuan it would be most helpful if you either (or did both of these things):
Please note: there are lots of things that aren't fixed yet, or even close to fixed (for example, the homepage right now just has a data-dump of paragraphs from other pages -- it's not been made into A Thing yet). It is not helpful right now to point out these very messy bits. It would be best to stay focused on the high-level structure, or diving in and re-writing.