Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTo convert Jekyll documentation to PDF with a clickable table of contents, first build the site as HTML, then pass the generated HTML to a PDF engine such as Prince or wkhtmltopdf. Jekyll converts Markdown pages with front matter into HTML; the PDF engine consumes that built site, not your Markdown source directly. For a page-level TOC, kramdown can generate a heading list; for a whole manual, a Prince workflow can build a TOC from the documentation sidebar.
Choose how the table of contents should work
There are two different TOCs to consider. A page-level TOC is a list of headings within one HTML page. A manual-level TOC gathers documentation pages into a book-like PDF, typically using the site’s sidebar or an explicit page list. Decide which you need before choosing the build configuration: a generated heading list on one page does not automatically assemble an entire documentation site.
For a TOC within a page
With kramdown, put * TOC followed by {:toc} where the heading list should appear. The page must also have the TOC front-matter setting required by the project or theme. The marker alone may not be enough; if it renders as literal text or an empty list, check the front matter and heading structure.
For a whole manual
Use the documentation theme’s PDF workflow, if it has one, or configure the PDF build to include the desired pages and their sidebar order. The documented Prince workflow uses page metadata and sidebar entries to determine inclusion and create a full TOC plus mini-TOCs on section pages. Its Jekyll How-to Guide describes output with page numbers in cross-references and running headers and footers as well. Treat those as capabilities of that documented workflow, not guaranteed features of every Jekyll theme or PDF converter.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
Prepare a PDF-specific Jekyll build
Keep the source Markdown, YAML front matter, permalinks, sidebar URLs and assets in agreement. Jekyll normally reflects the source folder structure in _site, unless permalinks change the output paths. The PDF process depends on the generated paths being resolvable, so a sidebar link that works in the web site but points to a missing or differently named output file can disrupt a strict conversion workflow.
-
Make a separate configuration file, for example
_config_pdf.yml, rather than changing the configuration used for the normal site. -
In that PDF configuration, set the print title and subtitle, identify the sidebar, select the site folder, and mark which pages belong in the PDF. The documented Prince approach uses page metadata and sidebar entries for this selection; adapt the fields to the theme’s actual configuration rather than copying settings from a different theme.
-
Check that the listed page URLs, permalinks and asset paths correspond to files that the build will generate under
_site. If the project uses a theme-provided list such asprince-list.txt, verify each entry against the output paths.Recommended: Crashes or Glitches? A Free Driver Scan Usually Finds the Culprit →Recommended: Fix Windows Errors and Clear Junk Files in Minutes - Free Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Keep Jekyll and gem dependencies reproducible with Bundler. GitHub recommends Bundler to reduce dependency-related build errors and environment bugs.
Jekyll is a static site generator built into GitHub Pages, but a local PDF workflow still depends on the project’s theme, configuration and installed gems. A PDF-specific configuration makes the output choices easier to review without changing the ordinary web build.
Rank #2
Build the HTML before converting it
Run the PDF configuration through the project’s Jekyll build or serve command. The documented workflow uses:
jekyll serve --config _config_pdf.yml
Use the equivalent command and configuration conventions for the project if it wraps Jekyll in Bundler or another build script. Inspect the generated HTML and _site paths before invoking the converter. A documentation theme’s Prince example specifically requires building an HTML web target even though the final deliverable is a PDF.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
-
Open the relevant generated pages and confirm the expected content and heading hierarchy are present.
-
For a page-level TOC, confirm the heading links appear and point to the intended headings.
-
For a whole manual, confirm that every intended page is present in the selected sidebar or page list and that its generated path exists.
-
Check that images, stylesheets and other local assets resolve from the generated HTML when the converter reads it.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Convert the built HTML to PDF
Choose the engine based on the output you need and the integration the project already supports. Prince has the most complete cited documentation-theme workflow here, including manual TOCs and print-oriented page features. wkhtmltopdf offers command-line controls for outlines, TOC-related behavior, page offsets and print-media selection. A plugin such as jekyll-pdf can reduce custom glue by generating PDFs from pages or collections when pdf: true is set in front matter or defaults, and accepts wkhtmltopdf-compatible settings. Check a plugin’s current maintenance and compatibility before adding it; the available evidence does not establish its present maintenance status.
Prince
Use the theme’s documented Prince command and input list where available. The converter needs the built HTML and must be able to resolve the pages and assets it references. The theme’s page metadata and sidebar conventions govern which content enters the PDF, so follow those conventions rather than assuming a generic command will infer the manual structure.
wkhtmltopdf
Point wkhtmltopdf at the generated HTML entry page or the HTML input appropriate to your project. Its controls include outline/TOC behavior, page offsets and print-media selection. Verify the command’s options against your installed version and desired layout; the specific command line depends on whether you are converting one page or assembling multiple pages, and no single universal command for Jekyll manuals is established by the available documentation.
jekyll-pdf
For page- or collection-level PDF generation, enable the documented pdf: true front-matter flag or configure it through defaults, then use the plugin’s wkhtmltopdf-compatible options. This is a convenient integration path, but it adds a gem dependency and does not remove the need to test page inclusion, TOC behavior and print styling in the resulting PDF.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Style and inspect the PDF
Web navigation, sidebars and interactive controls usually do not belong in a printed manual. Use a PDF layout or print stylesheet to hide web-only elements and apply print-specific formatting. The cited documentation theme uses a print layout that removes navigation and sidebars while retaining print formatting.
Review the actual PDF rather than relying only on a successful process exit. Check the TOC links, page order, page breaks, headings, cross-references, running headers or footers if configured, and every image. If the PDF engine has print-media controls, make sure the intended print CSS is active. Local and absolute asset paths need to be accessible to the converter; a browser-only path or missing file in _site may not work in the PDF process.
Troubleshooting common failures
-
Prince stops on a page or asset. Check for a misspelled or missing sidebar URL, permalink or asset. Compare the entry with generated paths under
_site, and inspectprince-list.txtor the theme’s equivalent input list. -
The TOC is empty. For a kramdown page TOC, verify the heading levels, the
* TOCand{:toc}markers, and the required front matter. For a manual TOC, check that the sidebar/page metadata actually includes the intended pages.Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
The PDF still shows navigation or sidebars. Switch to the PDF layout or enable the print stylesheet used by the theme. Building the ordinary web layout alone may leave web-only elements in the output.
-
Links or images are broken. Confirm the converter can resolve the generated HTML’s local or absolute paths and that the referenced files exist in
_site. Review permalinks and the paths emitted by the build, not just the source directory names. -
The build fails after dependencies change. Use Bundler to pin Jekyll and gem dependencies, then rerun the HTML build before troubleshooting the converter. This separates a Jekyll/gem issue from a PDF-engine issue.
-
The output is a PDF but does not read like a manual. Check that the PDF-specific page selection and sidebar order match the intended reading order, then inspect print CSS and page breaks. A successful conversion by itself does not prove the document is complete or navigable.
PerformancePC Slower Than It Used to Be?DriversOutdated Drivers Are Slowing You DownPerformanceWindows Errors? Fix Them Before They SpreadSpecial offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Or skip the browser setup
For a screenshot or PDF of a single accessible web page—not for assembling a multi-page Jekyll manual with its own TOC—ScreenshotNeo can capture a URL with one request. Its clean-shot workflow accepts cookie/consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; those steps can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and responses identify page verdict and billing status in headers. It also has an MCP server for AI agents. Plans include 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 shots.
See the ScreenshotNeo API documentation. This cURL example captures the Jekyll documentation homepage as an image:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://jekyllrb.com/docs/ -o shot.webp
That call is for a page capture, not a replacement for building and converting a complete manual with a clickable TOC. Sign up for ScreenshotNeo to get 1,000 screenshots a month free with no card.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frequently asked questions
Can I convert Jekyll Markdown straight to PDF?
This workflow builds the Jekyll site as HTML first, then converts the generated HTML. The HTML build resolves Jekyll content and paths before the PDF engine lays out the document.
Will a TOC link to PDF pages?
A heading TOC can link within its generated page, while a manual-level TOC depends on the PDF workflow and converter. Inspect the finished file’s links and navigation; do not assume that an HTML TOC automatically becomes a PDF outline or page-numbered contents list.
Which engine should I use?
For a theme whose documented workflow relies on advanced manual structure and print features, start with its Prince instructions. Consider wkhtmltopdf when its command-line controls or plugin compatibility fit the project, and weigh a plugin’s added dependency against the custom integration it saves.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
