Add caption headers to site table of contents

[Eric-Arellano]

This keeps the same order of docs, but adds section headers so it's more obvious what is what.

It also adds a page to <self> so that you can go back to the home page.

Before:

After:

[garrison]

I'm open to this, but it's bit unfortunate that the API references would then come before the tutorials, explanation, and how-to guides.

[caleb-johnson]

I'm open to this, but it's bit unfortunate that the API references would then come before the tutorials, explanation, and how-to guides.

I'm normally going straight to API when I go to various packages' docs, so maybe not strictly unfortunate. Also, the API contains info on all the tools, so I don't think it's so bad up there with the CKT blurb and Installation

It's funny you mention this, because I had thought the API at the very bottom was strange before

[Eric-Arellano]

I'm happy with whatever order you all think makes sense! And feel free to push commits directly to this branch.

[caleb-johnson]

I'll approve and let @garrison make final call on order and merge

[Eric-Arellano]

@garrison, one option is to have a 3rd category group called API and then it has the entry underneath called API References. I like that because API is huge when expanded. So when expanded, you avoid covering the rest of the ToC entries. Wdyt?

I'm not sure where Release Notes would go?

[coveralls]

Pull Request Test Coverage Report for Build 5555862224

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 90.713%

---

Totals
Change from base Build 5532982717:	0.0%
Covered Lines:	2559
Relevant Lines:	2821

---

💛 - Coveralls

[garrison]

This looks great, thanks.