Use markdown for formatting. At least the markdown docs will be readable in github. Make file name end in .md and verify that it shows up as formatted when viewing it in github.
This is a grab bag of additional documentation.
Write new documentation will be a list of outstanding bugs and improvements.
E.G. using a dropdown in a form to select chart type. A user should not be able to choose a chart type
that requires 2 groups if only 1 group is present in the URL. ...
description of other ways to invoke it with examples:
adding an a tag to the issue.index.html file (partly covered by #80, but add additional examples
of charttype)
format existing docs using markdown - lists, terms, and headings:
Replace the file: Understanding_Chart_Url.txt with doc/Understanding_chart_Url.md (so it will be properly
formatted as markdown by github).
Split from https://github.com/UMB-CS682-Team-02/tracker/issues/58. Place it in a document in the doc subdirectory of the repo. Git pull from main to get the doc subdirectory if you don't have it.
Use markdown for formatting. At least the markdown docs will be readable in github. Make file name end in .md and verify that it shows up as formatted when viewing it in github.
This is a grab bag of additional documentation.
description of other ways to invoke it with examples:
atag to the issue.index.html file (partly covered by #80, but add additional examples of charttype)terms, and headings: