Deployable version of `tracey web`?

[jamesmunns]

This might already be possible, but it would be cool to have a deployable version of the tracey web interface, similar to mdbook or cargo doc. The docs aren't super clear whether the generated dashboard is static-friendly or requires some kind active API surface.

[fasterthanlime]

This might already be possible, but it would be cool to have a deployable version of the tracey web interface, similar to mdbook or cargo doc. The docs aren't super clear whether the generated dashboard is static-friendly or requires some kind active API surface.

It does. But the path to this is making the backend "pluggable" as far the frontend is concerned, and then you can just ship static files.

I'm interested in shipping this.

[killercup]

I did a thing in #178 but it doesn't reuse the frontend per-se and instead tries to make static HTML directly. See it as an experiment at best, and please give feedback

[killercup]

Things that came up while I built my version and thought how I'd deploy this for other people to read:

• Instead of an index.html with a redirect it'd be neat to have an entry page. Could be the project readme or something else that makes sense to put on gh-pages and the like.
• Rendering one massive page per spec makes sense but rendering the spec split up by its original md files is also valid, and what mdbook would do. Then, frontend search is needed again.
• Showing covered items with less opacity makes less sense if this is for people to read. I'd rather flip it around and show covered/verified items as solid and unimplemented ones greyed out.

(Not sure what use cases you all have, I just started playing with this last week!)