# dasl.ing

DASL (Data-Addressed Structures, pronounced "dazzle") is a small set of simple, standard primitives for working with content-addressed, linked data. The design is inspired by subcomponents of the [IPFS](http://ipfs.tech) universe, but simplified to improve interoperability, decrease costs, and work well with the web.

This repository generates a website containing the DASL specs and more. Go to https://dasl.ing/ to read it!

## Contributing

Contributions are welcome! Here's how you can help:

- Feedback, questions, or bugs: Create an [issue](https://github.com/darobin/dasl.ing/issues)
- Minor fixes: Feel free to open a PR directly
- Larger changes or new specs: Please start with an [issue](https://github.com/darobin/dasl.ing/issues) describing your proposal
- Join a call: [Monthly sessions on Luma](https://luma.com/cid-congress)

## Developing

The site is generated by SISL (`sisl.js`) into `build/`, which is gitignored and never
committed. Every `.html` file in the root is a spec source; the build turns each one
into a published `.html` and `.md` under `build/`, next to a processed `index.html`
and the static files (CSS, fonts, banners). Deploys ship `build/` and nothing else, so
the spec sources, SISL's databases (`bibliography.json`, `people.json`,
`maturities.json`) and the tooling never reach the server.

A spec's maturity lives in `maturities.json`. It drives both the status on the spec's
own page and the label beside it in the index's spec list, so don't write those labels
into `index.html` by hand.

To work on the site locally, run two commands in separate terminals:
* `npm run watch` will re-generate `build/` on save
* `npm run dev` in a second terminal will open up a static server on `build/`. The
  static server does not hot-reload, so you'll need to refresh the page to see changes.

Please note that this project follows the [IPFS Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md). Happy hacking!