One more tip: scopes

One of the key features of ourbigbook is that everything in the tree is unscoped by default. E.g. the "Overview" article actually goes under ourbigbook.com/pioyi/oveview and not ourbigbook.com/pioyi/hydrogen-sulfide/overview as you likely wanted.

The reason for that is that this is the best way to make topics work: docs.ourbigbook.com/#ourbigbook-web-topics and topics is basically the only feature that justifies the project.

There are two solutions to model your knowledge:

1) (recommended in this case: make a longer more specific title "Overview of Hydrogen Sulfide" or "Hydrogen sulfied overview"

2) Use scopes. Locally the tree would look like this: docs.ourbigbook.com/#h-scope-argument

= Hydrogen sulfide
{scope}

== Overview

== Production
{scope}

=== Laboratory

=== Industrial

which would produce a tree structure as:

/hydrogen-sulfide
/hydrogen-sulfide/overview
/hydrogen-sulfide/production
/hydrogen-sulfide/production/laboratory
/hydrogen-sulfide/production/industrial

I should also note that I'm not sure if scopes are working perfectly via web UI, though if they are not I want them to.

One big reason I don't recommend scopes in this case is that there is currently no way to unscope things. What if later on you want to add a child of "Hydrogen sulfide" but you don't want for its url to be /hydrogen-sulfide/something? It's not currently possible. Though I would like to support it one day.

I would also just remove the Overview section and just dump its contents on "Hydrogen sulfide" itself, since the content of an article is basically always its own overview.

I would recommed using scopes only very sparsely when you go into extremelly specific tutorials about something, which are very unlikely to have topic hits by others, e.g. ourbigbook.com/cirosantilli/cia-2010-covert-communication-websites though even then I end up regretting it.

Anyways we'll see, maybe at some point people will prever to use just scopes and we'll go there more.