Skip to content
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

FEATURE : Documentation #22

Open
cDelage opened this issue Nov 19, 2019 · 2 comments
Open

FEATURE : Documentation #22

cDelage opened this issue Nov 19, 2019 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@cDelage
Copy link
Collaborator

cDelage commented Nov 19, 2019

What for

It wil be great to include documentation and learning section to new front Cerberus.
Idealy the information tab should contain the sections :

  • Documentation :
    - User guid
    - Developer guid
    - Changelog
  • Learning
    - User how to
    - Developer how-to
    - Tutorials
    - FAQ

It should be great to include more sections than cerberus-source for simplify user life.
I recommend using a single format for all sections to standardize our documentation.

Our proposed solution

Tools

the tools we can use :
Asciidoc : markup langage to script all documentation
Asciidoctorjs : framework to compile html file from asciidoc file

Steps

First step to implements :
We can construct docs folder in project root :
-> create tree into "/src/" to store .adoc files
-> create tree into "/build/" to store generated html doc files
-> create bin folder / compile_documentation.bat to generate documentation build

Second step :

  • Construct components to access docs/build folder and read html files.

We can display it in the tree of this type :

Finally :
It's great to include compile_documentation.bat in project build.

We begin POC locally,
give us your opinion in commentary to understand your expectations.
@Nouxx if you agree on our proceed method, i can commit the beginning of issues with the docs folder content.

@cDelage cDelage added the enhancement New feature or request label Nov 19, 2019
@cDelage cDelage self-assigned this Nov 19, 2019
@R-Loic
Copy link
Member

R-Loic commented Nov 20, 2019

Hello,
i agree with you for everything you proposed except the separation between user doc & dev doc. Not all team work this way. This might be not clear for new user.

@cDelage
Copy link
Collaborator Author

cDelage commented Nov 21, 2019

We speak about it today,
we concluded several points :

  • We will probably opt to build a separate application which will contain the documentation
  • Keep user documentation only framework
  • Be careful of clearly delimit the difference between tutorial and how to
  • the documentation must be linked to the framework version

We must respecify the need with the community

for me the ideal structure of doc application would be :

  • user guide : a technical guide of framework possibility.
  • how to : explain a specific topic of the application (how to create a testcase)
  • tutorial : 1 big tutorial for new user learning to use the importants functionalities
  • FAQ : response of current ask in community

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants