docsify
docsify copied to clipboard
Generate static HTML site (static site generation, SSG)
Eagerly waiting for this function, maybe it can be added to docsify-cli.
EDIT by maintainers:
- This is from #802 (The original Implementation)
- We can either continue on #802 or create a fresh PR for this (@QingWei-Li thoughts ?)
- docsify-cli implementation ref https://github.com/docsifyjs/docsify-cli/pull/55
- Original issue https://github.com/docsifyjs/docsify/issues/136
Sorry I don't have time to do now π£, if you are interested, you can contribute.
For comparison, maybe this is a start?
so why not use gitbook π
I found madoko
:
- via npm
- https://www.madoko.net
- https://github.com/koka-lang/madoko
- https://www.microsoft.com/en-us/research/video/madoko-a-scholarly-markdown
You can:
- output static HTML
- output PDF
- include files
- style code in code blocks
@jrappen that looks cool, but seems it does the same things that gitbook can do
@QingWei-Li I'm new to docsify, would love to see this feature. I'm interested in contributing, can you point me in the right direction?
@dietergoetelen Seems the SSR API can achieve this https://docsify.js.org/#/ssr?id=deploy-for-your-vps
Hi @dietergoetelen,
Now part of the compiler can run in Node, you can refer to docsify-server-renderer
. We can read the files and then compile them like docsify-server-renderer
do the same. Would you like to try it?
@QingWeil-Li Was this close because it's now possible? Wonβt fix?
@maoueh
GitBook is recommended if you need to build static files.
But GitBook is a paid product, It's only free for "non private" projects. Can we at least leave the PR Welcome?
@QingWei-Li
A really simple solution would be to just add a print-css and reference the browser print function with a simple button (printing to PDF can then be chosen by the user). What do you think?
+1 on the feature request.
@jrappen I stumbled upon Madoko a while back. The main issue with it is that it is written in Koka, which no one knows apart from its author Daan Leijen, who is also the author of that package. For a while it was hosted on CodePlex, and it was really difficult to find the sources, let alone understand them, or contribute. I suppose this is now on GitHub because MS acquired the company... The reference manual looks absolutely amazing, and it's difficult to think that only one person is behind this; but IMO that summarises the project well. It looks awesome, but it's a black-box, written in sanskrit, with a single contributor.
@egoist Have a look at the reference manual; it serves a different purpose than GitBook. Madoko was designed to write scientific publication-like content; it supports LaTeX maths, internal references, citations, and footnotes out of the box. GitBook is meant to be an advanced documentation-writing tool, oriented towards web-publishing. Let us not compare pears and apples.
@QingWei-Li can it output pdf? need!
+1 on the feature request.
+1 on the feature request.
https://github.com/egoist/presite might be useful here
Anyone that wants this feature, why do you want it? Has the live client-side markdown rendering been too slow for you? Is it hindering your user experience?
I am just curious, because performance updates for the sake of performance updates may not be as productive use of time compared to other features that are being planned. Please let us know if you encountered any performance problems that make a difference to the user experience (so far I haven't seen one that is significant, but it could be possible if you have giant markdown pages then that's an issue, for example).
@anikethsaha Since you listed this in v5, I'll re-open and add it to the 5.0 project so we can track it.
Mostly because static files are easy to deploy across a cdn Service like Netlify
On Sun, May 10, 2020, 15:50 Joe Pea [email protected] wrote:
Just curious, anyone that wants this feature, why do you want it? Has the live client-side markdown rendering been too slow for you? Is it hindering your user experience?
@anikethsaha https://github.com/anikethsaha Since you listed this in v5, I'll re-open and add it to the 5.0 project so we can track it.
β You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/docsifyjs/docsify/issues/136#issuecomment-626401785, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGTNWYJT5DYMQ5ELKDQPTLRQ4VSPANCNFSM4DEBBIDA .
@bountyx Markdown files are also static files.
Ah! SEO!
That's a good reason to serve HTML, to make things more indexable by search engines.
@trusktr there is an issue with plugins. most of the things in docsify is a plugin. we cant make them work if we don't have the DOM. So either we need to do it with jsdom
while but this won't give 100% accurate results.
This will be a blocking issue for v5.
Maybe also doesn't have to be for 5.0, it can be for "when it's ready". :) It's a bit complex.
Maybe we can build it on NW.js instead of JSDom.
@trusktr yeah, we can remove this from the roadmap, this will be blocking issue
π
+1 on the feature request.
I using docsify for a online converter:
- it can convert
opml
outline file tomd
; - then preview the
md
file using docsify; - and using the docsify server renderer, convert the
md
file tohtml
file; - then using
WeasyPrint
(python package) converthtml
toPDF
.
now i am blocked in the step 3. because docsify server renderer have some probreams:
- it can't set basePath to local location;
- I don't know how to save the rendered content to an html file at server.
need 2 function:
- generate static html files for all docs;
- genarate a html file for a specific doc;
We have a blocking issue as plugins won't work if there is no DOM. Many plugins are using browser's features like local storage.
So i am not sure how long it will take or even it will be done or not
Do plugins work with Docsify's SSR?