TIL how to build the documentation locally!

I have made some changes to our headlines and tested it locally :-)

I tried updating doc/Makefile to use --id-prefix, but unfortunately, this also prefixes ALL links in the markdown file, breaking references from .md to somewhere outside.

I'll ask upstream pandoc if there's a way around this, but I assume for now we can't namespace .md documentation, and need to be super careful with how we name our headings :-/

I'll ask upstream pandoc if there's a way around this, but I assume for now we can't namespace .md documentation, and need to be super careful with how we name our headings :-/

That means that we shouldn't make headings like Overview because someone else would probably want to have that as well. But prefixing with something like $lang overview should be fairly safe since it's kinda namespaced to one of the files.

After looking at the rendered documentation a bit closer, I think it would be good to just get rid of the User Guide heading, since there's no other header at the same level anyway. What do you think?

My thought is that it can be good to keep, the reasoning behind that is that I in the future would like to see that we manage to get something in to build things with composer.

And that would be it's own headline among the lines Developing guide on the same level as User guide.

But I already dropped one level in this PR 😄

Okay, yeah, that makes sense. I guess we could also document buildPecl and such, which should probably be under a different heading on that level. :)