Skip to main content

Veritran Docs

Estándares de uso

[en] Use standards are a set of guidelines, best practices and patterns that define which is the most efficient and effective way to perform a task, in the case of the Veritran Low-Code Platform, to design and build, set up and operate an app. Use standards also set the scope of what must be considered and addressed before you start doing so. They must be applied by the whole team, from the onset of the project, when the app specifications and user experience are defined based on the guidelines and requisites set by the client, and throughout the app building, setup and operation stages.

use_standards.png

[en] The benefits of following specific use standards include:

  • [en] Helping collaborators share the same language and work collaboratively and aligned.

  • [en] Creating apps under a robust UX design system and clear building guidelines that ensure app quality and performance.

  • [en] Enabling the frictionless reuse of the different functionalities and components of an app, which accelerates the building process and improves maintainability.

[en] What You'll Find Here

[en] This documentation provides detailed information on how the team should work to ensure that use standards are followed during the entire app building, setup and operation process. To achieve this, standards are subdivided and organized into sections where each section defines and explains:

  • [en] the required steps with links to the articles that detail each step,

  • [en] the role of the team members involved,

  • [en] the resources available, and

  • [en] the specific spaces where the tasks are performed.

[en] For example, in the case of the building standards, the design system section contains a brief definition and description of the design system stages together with a diagram and a downloadable table with a step-by-step guide to be followed by the team. The step-by-step guide also links to articles with detailed information on each step of the process and resources to be used by the team.

[en] We suggest you to keep this documentation open together with the resources linked at the beginning of each stage article, as you will use them during the entire process.