N.b. short, clear, encouraging.

Linked into all the quest and skill pages - "if you want to help contribute / change something, click here (-> Contributor)"

Which will mean the Quest dependencies will need to change.

(Types / tags on NPM dependencies? Add content to MD files?)

How?

• inc minor version

The explicitly is the key. Users need to know what version, and where from. And this needs to be easy to manipulate for contributors too. (It might just be a display thing, the rest coming from the fact this is based on Git and NPM.

Or the order the sections in a skill are tackled in (as they will build upon each other)

Option to host elsewhere (e.g. self-hosted static site)

At the moment, if you change any code (e.g. the .travis.yml) then a new NPM version will be created and pushed by the travis build.

It should only do this (and publish the NPM module too) when there is a change to the published content (e.g. something resulting from the publish script's run.)

For potential contributors

We need concepts of "depends on" (i.e. pre-requisite) which will then gives us basic ordering

And also contains (i.e adventures contain skills and experiences)

• Or do we just have "depends on" and then we can put meta-tags on this relationship?

Easy to take what others have shared and change it

• "Fork me on Github" banner on generated sites.

Auto-gen a contributors.md file? (Which is also published?)

My inablity to scope local variables strikes!

Early warning of errors in config files (lint-checking hooks on PRs?)

To encourage people to contribute.

Clarity as to the origin of the element I'm contributing to, and where I edit it, and how to see these changes in my consuming component (do you contribute to it in the quest, or in the skill?)

How?