You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue #13 proposes to add a Javascript TOC component for a within-page navigation. When a CreativeWork is part of a Collection then it would be useful to have cross-page navigation.
The dir codec in Encoda generates a root.json file at the top level - this includes all the properties for the works in the collection (including nested collections ie directories) except for content (which is encoded as HTML). This file could be fetched and used to
Each HTML file also includes the meta data for the parts of the collection, including the depth attribute. This would allow some Javascript to know where to fetch root.json relative to the current page e.g.
Just to clarify the intent here. We need a tree nav for getting between pages as is often seen on the left of documentation sites e.g. this one in the Gatsby docs
Just to point out that the encoda docs are now being self-generated (ie. getting generated by encoda itself) and producing a root.json file: https://stencila.github.io/encoda/root.json and JSON-LD in <meta> as above. You can click through to the docs for individual codecs from the "Formats" table. Should be useful for testing this, and other components.
Issue #13 proposes to add a Javascript TOC component for a within-page navigation. When a
CreativeWork
is part of aCollection
then it would be useful to have cross-page navigation.The
dir
codec in Encoda generates aroot.json
file at the top level - this includes all the properties for the works in the collection (including nested collections ie directories) except forcontent
(which is encoded as HTML). This file could befetch
ed and used toEach HTML file also includes the meta data for the parts of the collection, including the
depth
attribute. This would allow some Javascript to know where to fetchroot.json
relative to the current page e.g.The text was updated successfully, but these errors were encountered: