New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation Approach #98
Comments
TSC meeting discussion: question to Ian as to what the production ready process rather than if this is a prototype effort at this point. Eugene walked the team through the choices between DITA to Markdown. His recommendation was to use Markdown as the approach we would use, primarily because of the possible of additional resources to help with documentation. Decision is made on Markdown. |
Ian would like to demo the website. |
Here's the link to the artwork created by OPM They are in the standard formats including svg |
discussed creating more data for orders to show large amount. |
Looking for push of Gatsby pieces by the May 1st meeting. MIT license question about acknowledgment, Kip to Investigate that need. |
Can this issue be close? |
Yes, we can close this issue. Gatsby is most definitely the tool for our main documentation site the "GenevaERS General Documentation" website. The advantages are:
So this issue can be closed. |
It is proposed that we consider use of Gatsby as the documentation tooling for web presentation. To be discussed at the TSC meeting in Feb.
Discussion should be had on User's Guide, Reference, Developer Guide, Impact, Design, etc.
Additional discussion to be held on DITA vs. MD as well.
The text was updated successfully, but these errors were encountered: