Frontend

In Architecture, the project’s frontend is the main entry point for most people to get to know and use the project via its web interface. However, it was developed in large phases (launched in 2021 with modifications in 2022, with the addition of Querido Diário: Technologies in Education), and still needs documentation and more specialists who understand the project and know how to implement and evaluate best practices.

To structure the development of this important part of the project in a consistent, effective, and collaborative way, we need all contributors to start from a common base of definitions about what QD looks like and how it presents itself to the world. Let’s begin this conversation below.

Design system

The Querido Diário design system is being developed following the atomic design methodology. This document provides important information for project maintainers, both in frontend and UI/UX design. Currently, we are focusing on consolidating the design system’s foundation.

In this initial phase, we are working on two fundamental elements:

Style guide

Definition of the project’s basic visual guidelines.

Component mapping (atoms)

Identification and documentation of the most basic interface components.

After the foundation is consolidated, we plan to evolve towards organisms, pages, etc. This process will allow us to work on the QD interface collaboratively in a way that is more understandable for all involved.

Resources used

To consolidate the design system foundation, we are using:

Reference studies

The following studies were conducted by Juliana Holanda Bonomo, OKBR’s Civic Innovation ambassador, and will be used as a basis to guide changes in the project:

QD usability analysis

This study evaluates the current user experience and identifies areas for improvement in the interface;

QD personas study

This study provides insights into the typical users of Querido Diário, their uses, and goals.

Notes for maintainers

  • When developing new components, consider how they fit into the atomic hierarchy (atom, molecule, organism, template, or page);

  • Keep the documentation updated as new elements are added to the design system.