...
`, `...
\");\nepub.addSection('Chapter 2', \"...
\", false, false, 'chapter-2');\nepub.addSection('Epilogue', epilogueText, true);\n```\n\nFor the above the *Copyright* page will appear as front matter ahead of the table of contents, *Chapter One* will be standard text, *Chapter Two* will also be standard text but within the EPUB itself the filename used is specifically overridden (often to provide stable interlinking), and the *Epilogue* appears at the end but is excluded from the contents page.\n\nIn detail:\n\n- `excludeFromContents` allows you to add content which does not appear either in the auto-generated HTML table of contents or the metadata contents used directly by ereaders/software. This is handy for example when adding a page at the end of the book with details of your other books.\n- `isFrontMatter` means content is included as normal but this flag is passed into any custom content page generation function you may choose to provide (see [Custom Table of Contents](#custom-table-of-contents)). Front matter will also appear in your book *ahead* of the contents page when read linearly. Useful for dedication pages for example.\n- `overrideFilename` allows the filename (don't provide an extention) to be specified manually, which stabilises internal linking across sections. This was always possible using the auto-generated filenames (eg `s2.xhtml`), but whilst the naming was predictable inserting a new section bumped following sections further along the sequence (so `s2` becomes `s3` instead), which breaks internal links. Using a manually named section prevents that breakage by guaranteeing the link will always go to the expected place. This should only be relevant if you are doing internal cross-section links; general works of fiction for example won't usually need this facility.\n\n#### Text Substitutions\n\nA simple form of text substitution is supported. At any point in your content you may include placeholders like `[[COPYRIGHT]]`. When the EPUB is generated any such placeholders which match the *capitalised* name of a *metadata* entry are replaced with the corresponding metadata value.\n\nFor example, you could have a *\"Thanks for Reading\"* page at the end of your book which has the following content:\n\n``` html\nThanks for reading [[TITLE]] by [[AUTHOR]].
\n```\n\nWhen the EPUB is produced if your metadata sets a `title:` of *\"The Hobbit\"* and an `author:` of *\"JRR Tolkien\"* then it will generate this:\n\n---\n\nThanks for reading **The Hobbit** by *JRR Tolkien*.\n\n---\n\nThis means you can re-use content across multiple books, relying on the text subsitution to update that content based on the current book's metadata. Or you can refer to the author/title/series/whatever at any point within the book without worrying about consistent spellings for example.\n\n### Including Images\n\nIn [Setting the Metadata](#setting-the-metadata) the example metadata included an image:\n\n``` javascript\nmetadata.images = ['../test/hat.png'];\n```\n\nThis part of the metadata is an array of filenames which locate the source images on your system.\n(I strongly recommend you use relative paths in order to allow for documents being produced on different systems having different folder layouts.)\n\nThese images are automatically added into the EPUB when it is generated. They always go in an `images` folder internally. As they all go into the same folder they *should have unique filenames*.\n\nTo include the images in your content the HTML should refer to this internal folder rather than the original source folder, so for example `![](\"../images/hat.png\")
` in the above example.\n\n- Accepted image types are `.svg`, `.png`, `.jpg`/`.jpeg`, `.gif`, and `.tif`/`.tiff`.\n\n### Changing the Styling\n\nYou can inject basic CSS into your book. This allows you to override the basic styling to change how it looks.\nYou should use this sparingly - there is inconsistent CSS support across ereader devices/software.\n\nFor example the following ensures that in a flow of multiple paragraphs the first starts at the left margin whilst the second and subsequent paragraphs have their first line indented a little:\n\n``` javascript\nepub.addCSS(`p { text-indent: 0; } p+p { text-indent: 0.75em; }`);\n```\n\nIf you want to see the raw HTML in order to help with creating CSS then note that an EPUB file is just a ZIP file with pre-determined contents. If you expand it (you may need to rename it to a `.zip` file first) then you can see the individual section files inside.\n\nAlternatively see [Folder of EPUB-Ready Files](#folder-of-epub-ready-files) for how to write the EPUB innards into a folder instead of as a single file.\n\n### Custom Table of Contents\n\nThere is a default table of contents added into all generated EPUBs.\nIn addition to suppressing it (see [Setting the Metadata](#setting-the-metadata)) you can also create it yourself.\n\nYou do this by providing a callback function, a standard Javascript function which will be given a breakdown of the EPUB contents and is expected to return ready-to-use HTML for the table of contents page. You do this by passing that function as the second parameter when creating your document.\n\n``` javascript\nvar epub = nodepub.document(metadata, makeContentsPage);\n```\n\nThe above specifies a `makeContentsPage` function should be used to create the table of contents.\nHere's an example:\n\n``` javascript\nvar makeContentsPage = (links) => {\n var contents = \"