Developer handbook for contributions to the Altinn code base.
This should provide all basic information needed to get started with development on the altinn-studio repo. It should alto contain the information needed to make sure all developers write their code in a consistent way.
The guidelines should work as reference material, but it should also be possible to read throught the whole development handbook in a logical order so that new developers quickly get up and running.
The development handbook is a dynamic material and everybody should feel free to extend or correct articles when needed.
Guidelines for working with resources in Azure DevOps
Coding guidelines for back-end
Qucik guide for different commands
General guidelines and best practice for working with Cosmos DB
Guidelines for deploying
Coding guidelines for front-end
General coding guidelines
Information about how to get started
Information about version control with Git
Naming guidelines for Altinn Studio development
Nginx loadbalancing in studio
Information about routing with nginx
Setting up PostgreSQL for local development
RESTful APIs (Representation State Transfer)
Guidelines for designing REST apis for microservices in Altinn
Information about routing
Security is an important concern in all the phases of the DevOps cycle for Altinn 3.
Coding guidelines for tests
Branching information for Altinn Studio.
Flight rules for Altinn Studio
How to customize and configure Gitea.
A important feature with Altinn Studio is that it should promote developers to create reusable resources that can be reused by other developers.
Theming and styling
Solution for theming and styling conventions.
Troubleshooting of Altinn Studio.