jordwalke / paradoc Goto Github PK

Since Paradoc loads documents in a waterfall order, it takes around 5 seconds to render locally (using file:// protocol) or 30 seconds remotely.
The project contains 46 pages.

I would suggest displaying the current page first then load the rest of the pages later.

After digging into the codebase, I would suggest a change to page configuration.

• Root page (usually README.html or index.html) would has a new yaml header called pages that would list all pages in order.
• Child pages only need to define rootPage.

Benefits of this procedure :

• This allows easily move files around and re-ordering pages
• Deterministic sticky page headers order.
• Load pages in parallel

When there are a lot of pages, sticky page headers could be scrolled horizontally but there aren't any indications at all about it. We need to:

• Show indications that users could scroll horizontally(left arrow and right arrow when neccessary).
• Allow drag to scroll with mouse.

I can't understand what <continueRight /> is doing by reading the docs. And the name is honestly very confusing after talking to @jordwalke to know exactly what it does

To understand <continueRight />, let's look at a normal render when content is moved to the right side:

A  B
A  B
A  B
   B
C
C
C  

By adding <continueRight />, the vertical space between A and C is removed like this:

A  B
A  B
A  B
C  B
C
C  

Maybe the README.html points to the wrong file for recognition and origin information or the origin info file is still in the making. This is a young repo, so, just wanted to point that out 😉

This is an interesting idea and am curious how that repo will develop. Thanks for sharing.

Currently nodeMode only supports macOS and Windows