Hi colleagues, I’m trying to figure out if and how I can do a couple of things in Scrivener. One is to have side notes similar to the attached image, and the other is to have some paragraphs in an set block of a different colour (for highlights). I have found these very useful in text books, where some content is more an aside and some are key takeaways. If anyone can point me at resources covering how I can do this in Scriviner, that would be lovely!
Short answer: you can’t. Scrivener is not a page layout tool and has no support for this kind of task.
But you absolutely can use Scrivener to keep the sidebar and the main text separate for final formatting in your preferred tool.
Just a quick response before I turn in.
Scrivener itself is not about complex layout like that. For that, you would need to use it in combination with Markdown/Pandoc/Quarto or if you only need PDF as the output, with Typst.
I am in the process of developing a “pure Typst template” for myself which has margin notes, tip/alert boxes, code environment, etc. I have not yet worked on bibliography, and for the moment I use Affinity Publisher for everything preceding the ToC.
What I have so far compiles perfectly; it is very quick… first compile of a 60+ page document (recipe collection) takes somewhere between 2 and 3 seconds, as it downloads packages from a repository, subsequent compiles take under 2 seconds as the packages are already cached.
Let me know if you think you might be interested.
![]()
Mark
I would definitely be interested! I have multiple projects, some of which are more technical than others, so that sounds pretty interesting.
I realized I wouldn’t “do the layout” in Scrivener, but was hoping there was a decent way to capture the text that would go in sidebars etc in other text items so that I can compile it all together and still take advantage of the nice built in outlinging and so on.
There are several routes you can take in a program like Scrivener:
- As noted above, make use of its Markdown support instead of sticking solely with the rich text stuff. This is a pretty in-depth system, especially considering its integration with Pandoc. Some might say the sky is the limit, but it’s certainly one that edges towards programming the closer you get to the sky. Thankfully it starts out pretty simple, and the kind of thing you can pick up in a few days of reminding yourself with cheat sheets (if you’ve never used Markdown before). This is the route that I take myself, and the one the Scrivener user manual uses. (Download its source project.)
- Scrivener itself is a capable markup generator (which in part can help you generate Markdown). Typst was mentioned above, and another typesetting system it has a built-in project template for already (in the Non-Fiction category) is LaTeX. The idea with setups like these are to aim for creating a particular file type directly rather than going through a conversion engine like Markdown. The experience of doing so, while writing (not so much configuring), is not too dissimilar from rich text use. You’ll be working mostly with styles and outlining (section types), and having those tools do the heavy lifting for you.
- Sticking with the more “rich text” approach, the old stylesheet + template workflow is what publishers and designers have been using for decades to pull off stuff like the above screenshot. Nobody expects the writer to be doing any of that in their text editor, word processor or specialist writing tool. So you use styles to mark up “Sidebar box”, or “Call out box”, and then someone (or you) insert the marked up text into a template that has these things already designed to look right. At that point you’re using Scrivener more for its text tagging and assembly abilities, and ignore most of its formatting (or taking advantage of it for your own aesthetic preferences).
There are many details into each of those three main approaches, so you might as well jump in and say which sounds the most akin to how you like to work, or what you’d be most willing to learn. There are piles of threads on the forum for all of these, it’s just a matter of knowing which ones to pull up.
If you aren’t sure about any of it yet, one good thing to know is that all three can look remarkably similar from the source side of things. While you can write in pure raw Markdown from top to bottom, or LaTeX, most don’t! In fact some don’t use any at all, and lets styles and outlining, along with Scrivener’s built-in markup generators, do everything for them. If you had a look in my sample project, you’ll certainly see some markup, because I actually do prefer writing with it, but by and large much of the text could be confused with the third option.
The implication of that fact is that you may not need to decide immediately. Use styles, for everything that looks different from body text, learn how to use section types and architect your outline with them, and chances are you won’t have to really make a firm decision until you get well down the path.
Here’s a little trick to close, one that works no matter what approach you take: the <$include> placeholder, when linked to another item, inserts it at the point in the text where you place it. It’s a great way to insert tables, sidebars, boxes and other special elements you want to outline separately, so as to keep them agile, outlined perhaps by type, and easy to search through individually for their kind. Since they are inserted with a placeholder, they can also be replicated throughout the work for formulaic warnings, advice and such. I recall a lot of repeated instructions in textbooks, why type that in over and over when you can insert it many times, and edit typos out of them all, only once?
Wow, thanks for this detailed response. Markdown is fine for me actually - the main reason I want Scriviner is the outlining and file management and corkboard and so on. My normal go to for tech writing is sphinx (in rst, like a souped up markdown) and I am a programmer, so if that’s what gets me the most flexibility, that would be just fine.
