jesselawson / campfirejs-prototype

A tiny, pure JS tool for writing interactive stories and experiences.

Hello 👋🏼 I like to build and think about developer tools and ecosystems that cultivate curiosity.

Website: https://nullnotes.com

campfirejs-prototype's Issues

Simplistic, opinionated paradigm for mutable stories

It should be relatively easy to write a quick, mutable story with Campfire.

For example, let's say I want to create a tutorial on how to use it. The tutorial should fit on a single html page, with each tutorial section setup as a .page-# div.

There should be a way to automatically create some kind of inner link with a special identifier that will close the page it's on and open the next page in the sequence.

Perhaps something like this:

<div id="page-1">
<p>Clicking the second link on page 2 takes you here.</p>
</div>

<div id="page-2">
<p>This is page two. Go <a onclick="story.linknext()">here</a> for the next page, or <a onclick="story.linkprev()">here</a> to go back one page.
</div>

<div id="page-3">
<p>Clicking the first link on page 2 takes you here.</p>
</div>

Data saving system. Localstorage? DB?

Campfire should have a way to store data that can be retrieved at a later session.

LocalStorage is an obvious solution, and some discussion should be had as to whether there should be a database connectivity layer. Perhaps this would give rise to some kind of plugin support?

Reference/Query trigger status

Like switches, we should be able to reference a trigger to determine its state.

For example:

story.registerTrigger({
  label: 'created trigger feature',
  trigger: () => { /* something */ },
  then: () => { /* something else */ }

We should be able to query the status of that trigger, like this:

story.triggerStatus('created trigger feature')
// Returns false

or

story.fired('created trigger feature')
// Returns false

Update/cleanup Readme

• Add wiki links
• Add build steps for min version