Open miphilomath opened 4 years ago
@miphilomath -- Thank you for kicking this off. All of the above plans look good to me other than the following comment, How about removing the Developer Guide? API Reference and Project Structure are the proposed sections adding value. Project Structure can be documented in the Contributor Guide itself and API Reference can be a separate top-level section.
Yeah, I guess we can keep the contents of developer guide in contribution guide. I kept a separate developer page assuming that the page will grow bigger with details of Frontend and Backend components and applications detail later. But I guess, we can keep them in contribution guide until that happens.
Also, should I go ahead with the Pull request for the documentation as suggested above?
Since Junction's documentation is distributed at various places and requires restructuring, I would like to propose the following structure for the readthedocs documentation, suggesting appropriate location for the existing documentation on GitHub wiki. Creating a structure before writing pages will help us write individual pages and recollect them easily.
I suggest to have 4 level of documentation:
Welcome Page
User Level, to welcome more use of the project among speakers and by other conference organizers with following sections/pages.
Contribution page
Development Page, for developers working on the project
Structure of the project, detailing on the individual application
631
627
589