The following document contains a compilation of conventions and guidelines to format, structure and write code for the ESMF SDK JS Aspect Model loader.
Our code conventions are based on the Google Typescript Style Guide but detailed and adjusted for the needs of the ESMF SDK JS Aspect Model loader.
See CONTRIBUTING
This project uses the library Prettier and should also be created with it, so that a clear code can be created.
Developer documentation is put into a README.md placed in the project root. This should contain documentation like:
- Checking out the source code and getting it to run/build
- Mandatory (external system) dependencies and how to set them up (e.g. databases)
- Configuration options and how to apply them
- General important concepts that are relevant to working on the project but are not directly obvious from the source code itself. Links to further readings and information, e.g. wiki or other external sources.
User documentation (this includes technical documentation on how to use an application or tool from the SDK) should be on its own. It is written in AsciiDoc, rendered with Antora and the generated static content is publically hosted for direct user access. The source files of the documentation are placed in a subfolder /documentation from the project root. Documentation is structured so that it can be processed by Antora. This e.g. involves structuring the documentation files according to Antora's specification and organizing resources so that Antora can handle them. AsciiDoc's syntax is pretty close to Markdown, however it is way more targeted towards writing fully fledged documents and with its multitude of backends (HTML, PDF, ...) it is a very good source format. Publishing is realized by means of Github pages.