You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Specification section some topics are spread across multiple pages that should be combined into extensive single-page documents.
For example, the subsection about if clause has seven subpages detailing specific aspects of the language feature.
Most of them are fairly small with just a couple of paragraphs and a code example.
They would comfortably fit into a single document which describes if clauses in entirety. Each detail would still have its own subsection and can be directly linked to. But it's embedded in the larger context of the language feature with its different aspects. The page about case clause for example already covers all aspects in a single document.
User experience is improved because everything about the topic is handled in a single document and you don't have to navigate between pages for reading individual sub-features. The table of contents makes on-page navigation nice and easy.
As a bonus effect, integrating these sub-pages also improves navigability of the menu tree because there's less nested sections. If we can
This picks up an aspect brought up in #384. See Page boundaries for an initial analysis.
There are several section that I would suggest for merging up:
I like the previewed changes, any reason you haven't added them? Only thing is the "truthy and falsey values" page might need renaming, maybe to "logical operations" or something.
In the Specification section some topics are spread across multiple pages that should be combined into extensive single-page documents.
For example, the subsection about
if
clause has seven subpages detailing specific aspects of the language feature.Most of them are fairly small with just a couple of paragraphs and a code example.
They would comfortably fit into a single document which describes
if
clauses in entirety. Each detail would still have its own subsection and can be directly linked to. But it's embedded in the larger context of the language feature with its different aspects. The page aboutcase
clause for example already covers all aspects in a single document.User experience is improved because everything about the topic is handled in a single document and you don't have to navigate between pages for reading individual sub-features. The table of contents makes on-page navigation nice and easy.
As a bonus effect, integrating these sub-pages also improves navigability of the menu tree because there's less nested sections. If we can
This picks up an aspect brought up in #384. See Page boundaries for an initial analysis.
There are several section that I would suggest for merging up:
if
clause section +unless
clause (preview)while
clause section +until
clause (while)The text was updated successfully, but these errors were encountered: