Replies: 1 comment 1 reply
-
It's under very active development right now. Most of the engine and code bits are in place, so the bulk of the work is porting over the API documentation theme that makes use of the Statiq Docs pipelines and code analysis. Here's where we're at today:
Unfortunately this work is interrelated enough that it's mostly just me grinding. Getting all the bits to work smoothly in a unified development environment where I can work on all the projects at once was tricky but now that I've up and running it's going pretty quickly. Bascially the only thingg left on any sort of roadmap right now is "get the theme finished" :). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm running into a use case where I'd like a code documentation site and staying with Statiq for this is an attractive prospect, but I understand that the Docs library is in need of a rework.
Is there a proper roadmap available at this point or would you invite work being done to establish one? Having read some of your comments there, @daveaglick, it sounds like this was either ported from Wyam and is still relying on some of its code or it's using a much older version of the Framework library (I've not actually dug into the code to look).
If you could sum up exactly where we are on that, I can look at working with you to create a roadmap for release and then start laying down some code to bring it up to date or rewrite it from scratch, whichever you feel would be most appropriate. I do feel we should create a branch in the Statiq.Docs library just for this though since it sounds like it'll be a more involved change. At that point we can begin closing or prioritizing issues as appropriate.
Beta Was this translation helpful? Give feedback.
All reactions