![](\"../images/image-1.png\")
`.\n - `data` image as _blob_ or _base64 dataURI_.\n\nCall the `document` method with the aforementioned metadata object detailing your book.\n\n```javascript\nvar epub = new NodepubLite(metadata);\n```\n\nYou also have the option to generate your own contents page. Full details on this are shown further down the page.\n\n### Fill in the content\n\nThe bulk of the work is adding your content.\n\nCall `addSection` on your new document with a title and the HTML contents for each section in turn (usually a section is a chapter), plus extra options as follows.\n\n```javascript\nepub.addSection(\n title,\n content,\n excludeFromContents,\n isFrontMatter,\n overrideFilename\n);\n```\n\n| PARAMETER | PURPOSE | DEFAULT |\n| ------------------- | -------------------------------- | ------- |\n| title (required) | Table of contents entry | |\n| content (required) | HTML body text | - |\n| excludeFromContents | Hide from contents/navigation | false |\n| isFrontMatter | Places before any contents page | false |\n| overrideFilename | Section filename inside the EPUB | |\n\nFor example:\n\n```javascript\nepub.addSection(\"Copyright\", copyright, false, true);\nepub.addSection(\"Chapter 1\", \"...
\");\nepub.addSection(\n \"Chapter 2\",\n \"...
\",\n false,\n false,\n \"chapter-2\"\n);\n```\n\n_Excluding from the contents page list_ 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 - a common page which may not appear in the book contents.\n\n_Flagging as front matter_ still includes it but passes that flag into any custom content page generation function you may choose to provide. Front matter will also appear in your book ahead of the contents page when read linearly. Useful for dedication pages, for example.\n\n_Override the filename within the generated EPUB_ allows the filename (don't provide an extention) to be specified manually, which enhances 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 further sections further along the sequence (so `s2` becomes `s3` instead), breaking internal links. Using a manually named section prevents that breakage.\n\nThis should only be relevant if you are doing those internal cross-section links; general works of fiction for example won't usually need this facility. See the end of chapter one's content and the definition of content two in the example folder for sample usage.\n\n### Optionally add some extra CSS\n\nYou can inject basic CSS into your book.\n\n```javascript\nepub.addCSS(`p { text-indent: 0; } p+p { text-indent: 0.75em; }`);\n```\n\n### You can also choose to make your own custom contents page\n\n_A standard contents page is included automatically, but can be overridden._\n_You can also suppress the contents page entirely; see the metadata section above._\n\nYou can create your own by passing a second parameter when creating a _document_ - a function which is called when the contents page is being constructed. That function will be given details of all the links, and is expected to return HTML to use for the contents page.\n\n```javascript\nvar makeContentsPage = (links) => {\n var contents = \"Thanks for reading [[TITLE]] by [[AUTHOR]].
\n```\n\nWhen the EPUB is produced and opened, if your metadata was set as per the book \"The Hobbit\" by \"JRR Tolkien\", then it will look like 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, or refer to the author/title/series/whatever at any point within the book without worrying about consistency or maintenance.\n\n## Reminder\n\nThis is a utility module, not a user-facing one. In other words it is assumed that the caller has already validated the inputs. Only basic omission checks are performed.\n","readmeFilename":"README.md"}