Support for Offline HTML Rendering #269
Replies: 2 comments
-
Hey Vasu! 👋 Great question — I’ve run into similar issues when needing documentation to work offline on internal systems. ✅ Two approaches to fix this:1. Generate a fully self-contained HTML fileYou can try using a post-processing tool like: These tools can take your generated HTML and automatically inline:
Run it like this: npx inline-source input.html > output.html This will give you a single 2. Replace CDN links with local pathsIf you're able to tweak the template or HTML generator config:
<link rel="stylesheet" href="assets/bootstrap.min.css" />
<script src="assets/jquery.min.js"></script>
<script src="assets/bootstrap.bundle.min.js"></script> This method works great if you’re serving the HTML through a static site or file browser in a local environment. Let me know which route works better for your setup — happy to help with automation scripts if needed. Hope this helps you get fully offline-friendly HTML! 🚀 |
Beta Was this translation helpful? Give feedback.
-
Hi Baljir, Thank you for the quick response! I'll try this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm using
peakrdl-html
to generate documentation from SystemRDL. However, the generated HTML includes external links to resources like Bootstrap and jQuery (e.g., via CDN). This causes the output to appear broken when opened on systems without internet access (like internal build servers and cadence chamber).Is there a way to:
Thanks in advance!
Vasu
Beta Was this translation helpful? Give feedback.
All reactions