Hey! Some unsolicited feedback from someone very very new to this :)

I was looking for a new method to format invoices with specific layout requirements (i.e. some text at the bottom, a table, etc). I considered rendering html but most of the headless renderers seem like hacks and there's other issues with pdf output, colorspaces, etc, and I thought a specialized tool would be better. You have a prominent comparison to in-design that talks about how the same stuff can be done with frames in Sile, which sounds perfect.

The manual however first mentions frames on page 70 (frames and page layouts) and immediately starts talking about cropmarks and visualizing frames without anything about what frames are or how to even use them in the first place.

An actual discussion of frames is hidden in "The nitty gritty" on page 105 which I only stumbled on by chance as I was about to give up and look for alternatives.

So these might not all be appropriate, but just dumping some thoughts:

• I'd really like a "first-principles" approach to documentation, starting with the basics and ending up at advanced features. My guess is the real basics are "frames" and "flowed text" (blocks and inline content).
• I'm sure your primary audience is people writing papers, but people doing document layout I don't think are fewer globally and it's a significant differentiating feature for sile. Considering that, maybe a separate "guide for designers" would be reasonable? Or splitting the manual up, with a "choose your path" link at the start to the guide that's most appropriate?
• Regardless, introducing frames before introducing frame packages would probably make the guide more comprehensible. Even if it's just a short note that says that the default blocks are frames and points to the later more thorough documentation.

I think this project is really cool and it ticks a lot of my personal checkboxes so I'd like to dig into it more!