Should: 1. each chapter contain all guidelines or 2. a flat list linking to them and each guideline is its own page?

[PLeVasseur]

Now that we have each guideline in its own source file to reduce merge conflicts, ...

the question becomes one of should we, when rendering the document:

1. have each chapter contain all guidelines (as it is today)
2. have the chapter be a flat list linking to each guideline on its own page?

I'm partial to the latter, as it makes each chapter's landing page less imposing, but I'm up to hear thoughts.

[rcseacord]

Each coding guideline should be in a separate file.

[felix91gr]

Each coding guideline should be in a separate file.

That's not what Pete is asking, I believe. Now all guidelines lie in their own source file.

What he's asking is about the layout of the rendered webpage.

[felix91gr]

@PLeVasseur I'm partial to the latter as well. There are many things I would love to change about the current layout, and this one is pretty close to the top :3

[rcseacord]

OK, it should still be rendered on separate pages. This will make it easier to render, and also easier to link to a specific rule. Also easier to make links to specific paragraphs. Easier to make links to specific sections of a particular guideline.