Doc typos and suggestions #19
Description
On the CSV plugin page: the link in Refer to this section of the example for more information is invalid.
On the JSON plugin page: the line The following is the output from the comparison is inaccurate; the section seems to have been moved preceding to that line of text.
On the extending the CSV plugin page: the line "To set the index, we set the value of index is calc_options should use "in" rather than "is".
On the creating a plug-in from scratch page, there is the typo "specuialized".
The plug-ins API page lacks important details on the abstract methods, such the expected form of each return value, or the scope of each function and its place in the program flow. I was able to only mostly infer these details from the examples.
Suggestions that might be substantially more effort than typographical fixes or link maintenance:
- On the tutorial-style pages (e.g. CSV plugin extension) is that it would be helpful to highlight the changed lines in some manner.
- The CSV plugin page has a helpful API for available options. There isn't one for JSON. In general, the extension pages seem to have inconsistent structure in this regard.
- I believe the CSV plugin extension example was quite helpful, but had a lot of trouble figuring out how to navigate to it except directly by URL. I'm not sure which page links to it, but it could use more prominent linking, perhaps.