I have four examples of static wikis, as of this writing. I keep track of them in a few ways. This page captures some relevant links.
I track all of my public wikis in a roster with a separate section for the static wikis:
ROSTER wiki.dbbs.co/eric-dobbs
This first example puts the wiki in a subfolder of the github repo. I think there may be advantages to having a level in the folder structure that’s for notes about GitHub and is separate from the part that is the wiki. Though I have not yet taken advantage of that level.
deploy.wiki.do
hosted at github ![]()
wander.dbbs.co
hosted at github ![]()
explore.dbbs.co
hosted at github ![]()
turtle.dbbs.co
hosted at github ![]()
.
- [ ] see if we can generate the links to the various wikis by parsing the roster on the page.
Our first attempt failed because the roster plugin uses a different method name for providing the roster data. It doesn't conform to the expectations that are encoded in the `frame.sources()` function.
import * as frame from 'https://wiki.dbbs.co/assets/v1/frame.js'; export async function emit(el) { const {page} = await frame.context(); el.innerHTML = `<pre>${ JSON.stringify(page, null, 2) }</pre>`; }
In the frame below we can view the results.
//wiki.dbbs.co/assets/pages/js-snippet-template/esm.html HEIGHT 400
See also Static Import Snippet