-
Includes use examples, test cases and API documentation to facilitate understanding and customization of models.
-
One of Avoc's goals is to be easily extendable, making the addition of new features or services a handy endeavor. Technical documentation should be added to explain the code architecture and how to ad…
-
Please revise chapter. Divide it to **Functionality** (description of what is delivered in 1st prototype, should correspond with the Excel) and **Future work** (everything else). Also **Technology opt…
-
Please revise chapter and subchapters. Divide it to **Functionality** (description of what is delivered in 1st prototype) and **Future work** (everything else). Provide links to currently available AP…
-
Please revise chapter. Divide it to **Functionality** (description of what is delivered in 1st prototype) and **Future work** (everything else). Also **Technology** chapters should be revised and only…
-
When integrating Salt form controls with `react-hook-form`, there are a few issues identified to make consumer's life easier. This may include bug fixes to the component, or improved documentation or …
-
I thought of creating a technical documentation to also have some transparency of what this server is "made of"
A couple bullet points:
- general overview of the two physical servers
- docker setup
…
-
# Prerequisites
Please answer the following question for yourself before submitting a feature request.
- [ ] I checked to make sure that this request has not already been filed
# Motivation
…
-
A large part, I believe, of why RGBDS maintainership is not user-friendly, is the lack of technical documentation. The codebase has a lot of implied conventions, organization, and behavior, which are …
-
Various types of documentation based on needs. Technical, end user, tester, layperson, etc.