Christopher Joel

Noosphere doesn't have its own logo, but it should! Once we have one, we can add it to the README, and also include it in static HTML output implemented in...

As we implemented #51 , we didn't have very many static files (that is, files that did not need to undergo any transformation) to write. At the time of this...

As of #51 we will have a basic facility for rendering spheres as HTML. But, we don't yet include backlinks in the rendered output. Backlinks are a special case that...

As of #51 , we have implemented basic 1:1 generation of HTML for Noosphere content. However, some kinds of content may be best served over the web when rendered with...

As of #51 we will have landed a basic facility for generating static HTML from the full history of sphere content. In the basic case, we avoid re-generating HTML for...

As of #51 , we will have basic rendering of a sphere as HTML in place. We don't currently have a treatment for links that go nowhere. In the Subconscious...

As of #51 , we will have basic sphere-to-HTML generation landed. In the course of that change, it became apparent that we will need a good, deterministic strategy for deriving...

Currently, spheres mainly consist of a single content type: `text/subtext`. However, in the fullness of time we want Noosphere to be an appealing storage and exchange layer for arbitrary content....

After #37 is resolved, we will have a relatively high-level FS-like API for writing files to - and reading files from - a Sphere. The write side of this API...

Currently we have built everything around the most essential - and most limited - DID method: key. Key is great because it is very simple and easy to get going...