Separate Tasks for Users: Creating Content and Customizing Site
Ideally, workflow, documentation, and design will take into account that actually documenting or creating content is a task that should generally happen independently of customizing a site. Currently they often happen in parallel and I think this has proven confusing for people unfamiliar with documentjs (and especially designers).
this is here because milestones don't support markdown as well as issues
This issue represents what could be considered an ideal "Documentation Product".
A core product that focuses on reading files, converting that to something like a
docMapand exporting that to consumable format.
The core product should be more or less agnostic to the types or format of those files, and to the final format. Instead it should focus on:
With this core product in place, we might likely create two different extensions that can work together: a "js" and "css" extension. They would focus on meeting the needs of their user bases.
We need a name for the core product. Ideally, it should fit in well with "DocumentJS" and "DocumentCSS".
I think something like the following in
package.jsonfor each released version:
And then something like this for the main site:
The text was updated successfully, but these errors were encountered: