# juntossomosmais/frontend-guideline

📝 Front-end Guideline by Juntos Somos Mais

Repository: https://github.com/juntossomosmais/frontend-guideline
Canonical: https://ross.abutalabs.com/products/frontend-guideline
Homepage: https://juntossomosmais.github.io/frontend-guideline/
License: MIT
License Family: permissive
Topics: frontend-guidelines, frontend-guide, coding-style, code-style, frontend, css, html, javascript, react, vue, good-practices, patterns, patterns-design, hacktoberfest, typescript
Last push: 2025-11-10T12:13:42+00:00

## Health v2 (maintenance only)
Score: 55/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 51, release rhythm 35, longevity 100
- inputs: {"age_days": 1827, "days_push": 296, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1144, forks 54 (observed 2026-08-28T04:03:45.100247+00:00)

## What it is
A living documentation of front-end coding standards and best practices maintained by Juntos Somos Mais, covering HTML, CSS, JavaScript, TypeScript, React, Vue, Git, testing, and architecture. It is published as a webpage to help developers working on the company's projects follow consistent conventions.

## Use cases
- learn front-end coding style conventions
- set up team coding standards for HTML, CSS, and JavaScript
- find React and Vue best practices and patterns
- standardize Git workflow and commit practices across a team
- reference guidelines for TypeScript and testing in front-end projects
- onboard new developers to a company's front-end conventions

## When to choose
- you need a real-world reference for building your own front-end style guide
- you want examples of good vs bad code patterns for React, Vue, or TypeScript
- you are onboarding developers and want documented coding standards
- you want inspiration for architecture, Git, and testing conventions in front-end teams

## When to avoid
- you need an executable linter or formatter rather than written guidelines
- you require a complete, exhaustive specification of front-end practices
- you need tooling that enforces rules automatically instead of documentation

## Facets
- artifact type: learning-resource
- maturity: active
- function: documentation, developer-tools
- domain: frontend, web-development, documentation, tutorials
- platform: -
- tags: coding-standards, style-guide, frontend-guidelines, react, vue, typescript, css, html, best-practices, web-server

## Member repositories
- juntossomosmais/frontend-guideline (main) score 55

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:45.100247+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:34:44.963068+00:00, confidence not recorded.
  - readme: https://github.com/juntossomosmais/frontend-guideline (fetched 2026-08-28T04:03:45.100247+00:00, sha 547216db42ea)
  - homepage: https://juntossomosmais.github.io/frontend-guideline/ (fetched 2026-08-29T12:40:10.075036+00:00, sha a97c01429569)
- Data as of 2026-08-30T08:39:29.467469+00:00.