Hi.
There should be like a “headline” button, and subheadlines etc. And an option for the size, color etc of each headline, subheadline… Then it should be possible to make a table of content, that automaticly sets up all the headlines and subheadlines … the table of content makes it self (ofc u can edit it!)
People should be polite when they post here. And they should use the word “please” sometimes. And then they should remember that this here is the space for wishes, not demands (ofc, they can edit their posts after submitting them!).
r. 
When Keith responds, he will probably tell you that those are layout and design functions, and lie outside of Scrivener’s scope.
Katherine
The first issue - headlines and subheadings and so on - is “Styles”, which is something that comes up from time to time here. The trouble is that Scrivener uses the OS X text system, which doesn’t have a proper styles system built in, and which isn’t really set up for something like this. But also, because Scrivener uses multiple documents, updating styles would entail trying to update multiple documents on disk, many of which the user cannot see, which is problematic. I am looking into this, though, as another developer has recently had some great ideas in this area.
As for ToC, that is indeed the domain of a full word processing or layout program such as Word, and should be generated after you compile and export.
All the best,
Keith
I think the thing about styles and Table of Contents is this:
In Word, you need to apply styles to headings in order to generate a ToC. Working in Scrivener’s binder, the ToC is (in most cases) done, but Apple’s Text System has bad support for styles. The combination results in you making a ToC as you organize your project in the Binder, but then have to redo it all over again once you export to Word or other word processor. It seems a shame to not have your work preserved.
Of course, this is by no means Scrivener’s fault. I’m just articulating what I think is the nexus of the problem between poor style support from Apple, and wanting the ToC which you’ve already generated in the Binder not to be lost on export.