Repository navigation
docs product landing content
State: LOCAL_DONE — APPROVED, 2026-10-05. Scope: documentation and two static wireframe SVGs only; no website code, dependency, remote record or publication. Owner: P25-T01 under the static landing plan (rules B-BR-L01–L07, use cases BUC-L01–L05). T01 wireframes and tokens approved by maintainer (D-L05).
This contract freezes what P25-T02–T05 build. Changing copy, section order, tokens or a claim class goes back through this document first.
For the landing, use Manrope for headings, CTAs, navigation, cards, prices and
emphasis (700/800 for headings and 700 for prices); use Source Sans 3 for
long text, descriptions, FAQ answers, legal copy and informational subtitles
(400/500). This supersedes the system-only family row below. Self-host official
variable WOFF2 Latin/Latin Extended subsets, with font-display: swap, system
fallbacks, content-hash filenames and original SIL OFL 1.1 notices. Preserve the
approved vector wordmark; this does not authorize changing mobile typography.
Need/license/security provenance: landing/static/assets/fonts/provenance.json.
No runtime font CDN, new package or tracker is added. Include font bytes in
initial-transfer measurement and inspect layout/contrast after loading/fallback.
The follow-up visual/tutorial request uses branch landing; see the
bounded redesign plan.
The home opening introduces the genuine app gallery and tutorial section.
Only actual app captures may appear in mockups or step walkthroughs. Tutorial
captures come from docs/assets/app-tutorial
and follow its capture contract:
derivatives keep the capture stem and quoted app labels match the current
pt-BR strings, so a changed app screen points at the page or field to update.
| Path | Purpose | Indexed / sitemap | Notes |
|---|---|---|---|
/ |
Product explanation, source distinction, links | Yes / Yes | One H1; six content sections plus footer |
/privacidade/ |
Privacy statement (B-BR-L07) | Yes / Yes | Derived from maintained policy; see Legal pages |
/excluir-conta/ |
Web path to request account/data deletion | Yes / Yes | Required by Google Play for apps with account creation |
/termos/ |
Community terms | Yes / Yes | Reporting/moderation rules from the moderation policy |
/guias/ + 3 evergreen guides |
Education (P26) | Yes / Yes | Retained unchanged by the redesign |
/como-usar/ |
Tutorial hub: grouped chapter links, step counts, availability labels | Yes / Yes | New in redesign (LR15); crawlable links, no placeholders |
/como-usar/<slug>/ |
30 chapters, one per TU01–TU30 slug frozen in the tutorial catalog | Yes / Yes | New in redesign (LR16–LR24); pending chapters show a factual note, never invented screens |
/404.html |
Real 404 | No / No | Short message with links to home and repository |
This contract does not cover a blog, dashboards, forms, analytics or a newsletter. Guides, city pages and translations are owned by the organic growth and multilingual contract, per decision 026.
Home section order for the redesign (plan §Visual direction): compact header →
text hero with an authentic Android-home mockup (LH01 amendment below) → quiet principles strip → app gallery
(#aplicativo, existing anchor kept) → feature stories → tutorial teaser
(#tutoriais, new) → source explanation (#fontes, new) → project/privacy
(#o-projeto, existing anchor kept) → FAQ (#faq, new) → availability
(#disponibilidade, new) → footer. Existing anchors #como-funciona and
#aplicativo/#o-projeto keep their names; new anchors land with their
sections (LR10–LR12/LR15), never as empty targets.
Chapter slugs are frozen to the parenthesized slug in each TU01–TU30 catalog
heading (e.g. TU02 → /como-usar/escolher-cidade/); never renumber chapters,
never add city/keyword doorway pages. Hub groups: driver/discovery
(TU01–TU10), accounts/participation (TU11–TU21), representatives/tools
(TU22–TU28), help/offline (TU29–TU30). Availability labels: chapter headers
use Disponível (captured), Em breve (accepted capture, chapter pending) or
Planejado (gated per LR01); the prelaunch store notice stays
Em breve na Google Play (plain text, B-BR-L03) until a verified listing.
Public wording follows the class of each capability. Classes are checked against repository state on 2026-10-05; none of them is a production claim.
| Class | Meaning | Allowed wording |
|---|---|---|
| E1 | Exists in the preserved Android code and was released earlier under the previous name (APK on the upstream repository) | Present tense, framed as the project's foundation; no download link to the older release (B-BR-L03) |
| E2 | Integrated in this repository (backend and Android phases merged), not released, device validation owed | Future or “em desenvolvimento” wording |
| P | Planned only | “Planejado” wording, never present tense |
| Capability | Source | Class |
|---|---|---|
| Browse ANP weekly price surveys by fuel, state and city; works offline | README imported features | E1 |
| Up to 3 vehicle profiles and estimated full-tank cost | README imported features | E1 |
| Optional one-shot device location, navigation to Maps/Waze, local price-drop alerts | README imported features | E1 |
| Community price observations, source/date/condition display, “unknown/disputed” outcomes | Product contract, PROGRESS P19–P24 | E2 |
| Photo contribution with private evidence limited to 24 hours | Local media policy, PROGRESS P21 | E2 |
| Free accounts (username + saved account key; provider/email paths code-present but device-gated, tutorials pending proof), ratings, 280-character comments, votes, reports |
Free account access, moderation policy, PROGRESS P22, LR01 route audit (AuthViewModel, AnpNavGraph) |
E2 |
| Paid optional hosted benefits | Product contract (LATER) | P — not mentioned except the “payment never buys trust” commitment |
| Ethanol-versus-gasoline comparison | No verified feature | Excluded from copy and FAQ until a feature exists |
| “Cheapest near me”, savings figures, coverage claims, user counts, ratings | No evidence | Forbidden (B-BR-L01) |
Frozen strings for the home page. Section order matches the wireframes. Brackets show the store state.
Title (50 characters): abastevo | Preços de combustíveis com a comunidade
Meta description (146 characters): Projeto de código aberto para consultar preços de combustíveis com fonte e data visíveis, separando observações da comunidade e referências da ANP.
H1 (owner-approved SEO-21): Preços de combustíveis por estado e cidade, com dados da ANP with the slogan Mais informação para quem vive na estrada. retained below it as <p class="lp-slogan"> (strings loaded per locale from landing/content/i18n/{locale}.json under home.hero).
Lead: Encontre preços de combustíveis, veja dados da ANP e conte com a comunidade de motoristas.
Status line: Em desenvolvimento. O aplicativo para Android ainda não foi publicado.
Hero buttons: Ver no GitHub (open-source project, official CC0 GitHub mark, new tab) + Em breve no Google Play (honest non-link pill in prelaunch with official CC0 Play mark; verified store link only when published, new tab). No cheapest/savings/coverage/ranking promises anywhere: "melhor preço", "pagando menos", station counts, live maps and ratings are forbidden. Illustrated scenery and map lights are decorative, never station coordinates or coverage evidence.
Secondary action: Copiar link copies the repository URL without navigation.
Store notice [prelaunch]: Em breve na Google Play (plain text). [published]: Ver na Google Play, one link or the official badge, in one place only.
Illustrative comparison (heading Comunidade e ANP, lado a lado; label Exemplo ilustrativo · dados fictícios): two cards with the fictional place Posto Exemplo and the fictional value R$ X,XX; the community card reads Observação enviada por pessoa · há algumas horas · apoio visível; the ANP card reads Levantamento publicado pela ANP · semana da pesquisa · não é preço da bomba agora. Example values are always visibly fictional (no realistic price); text alternative: “Exemplo ilustrativo com dados fictícios: a mesma pergunta respondida pela comunidade e pela referência da ANP.”
Como funciona: 1 Consulte — Escolha cidade e combustível e veja os preços disponíveis, cada um com fonte, data e condição. · 2 Confira — Veja se o preço vem da comunidade ou da referência da ANP e quando foi registrado. · 3 Contribua — Quando o app estiver disponível, será possível enviar a foto de um preço (planejado).
Para quem é (optional; include only if each line stays verifiable): Motorista particular — Quem abastece com frequência e quer comparar informações com fonte e data. · Motorista de aplicativo — Quem roda muito e precisa estimar o custo de encher o tanque. · Pequeno frotista — Quem cuida de poucos veículos e quer organizar o custo de abastecer. (vehicle profiles and tank estimate are E1).
O projeto: Código aberto, com fonte e data à vista. Participar da comunidade será gratuito; pagamento nunca aumenta a confiança de um preço (planejado). plus link Ver código no GitHub.
Privacidade em resumo (each line must stay true at publication, see legal pages): Consultar preços não exige conta nem localização. · Este site não usa cookies nem rastreadores. · Fotos de comprovação serão privadas, apagadas em até 24 h (política do projeto). · Código aberto sob licença MIT.
Aplicativo / Acompanhe o projeto: Android · Em breve na Google Play and Acompanhe o projeto pelo GitHub; este site não pede cadastro nem e-mail. Ainda não há versões publicadas. Link: repository. The repository currently has no releases and an empty releases feed (checked 2026-10-05), so the Releases page and releases.atom links appear only after a first release exists; the older release on the upstream repository is not linked.
Perguntas frequentes (native <details>; answers to be written from the sources named, no rich-result goal): Como saber o preço de combustível de um posto? (describe source/date/condition display and the “desconhecido” outcome; E2, future wording) · O que é a pesquisa de preços da ANP? (verify against the official ANP page when writing the answer; a dated reference, not the pump price now) · Qual a diferença entre preço da comunidade e da ANP? · O aplicativo será gratuito? (community participation free; optional future paid benefits never raise trust; planned).
Footer: links GitHub · Privacidade · Excluir conta · Termos · Contato; text Código aberto sob licença MIT. Não afiliado à ANP. Dados de preços da ANP: gov.br/anp. Marcas e nomes citados pertencem a seus titulares. and a pointer to TRADEMARKS. The Google brand attribution is added only at store activation, copied from the guideline current then.
Google Play check (source and date recorded, as required): Play Console Help, account deletion requirements, read 2026-10-05: an app that lets users create an account must provide an in-app deletion path and a web link where users can request account and data deletion; this applies even if parts of the app work without an account; Data safety deletion questions must be completed. User Data policy, read 2026-10-05: a valid privacy policy is expected in the store listing and inside the app, and data practices must be disclosed in the Data safety section. This is a dated reading of Google's help pages, not legal advice or a compliance claim; it is repeated at listing time.
| Page | Content sources | Must state | Must not state |
|---|---|---|---|
/privacidade/ |
Security and privacy plan, location/media policy, free accounts, backend notice draft | Data categories (device contributor key, account email/provider identity, photos, location, price facts), purpose, retention, who can access, rights, backup aging, contact (D-L04); site uses no cookies/trackers | Legal approval, response deadlines (legal review sets them), shipped status of unreleased features |
/excluir-conta/ |
Rights workflow in the privacy plan, account erasure rules | How to request deletion without the app (contact channel), what is deleted, what remains anonymized, backup delay up to the backup horizon | Automated deletion that does not exist; identity disclosure without proof |
/termos/ |
Community moderation policy | Reporting, reviewed removals, no automatic deletion by votes, free participation, MIT software license vs. name/logo rights | Moderation powers that do not exist |
Retention reconciliation (resolved). The README and the media policy state that app-owned photos expire within 24 hours across all copies. The retention table in the privacy plan lists sanitized evidence at 14 days; that line is the earlier v1 baseline, and the same document states that the P15 media target replaces it. The media policy supersedes it and records the 14-day behavior as an implementation gap until forward changes pass tests. Decision: public wording uses 24 hours, labelled “política do projeto”, never as a guarantee for released software until the production release evidence exists.
Documentation gap found (blocks T03 wording, not T02). The backend privacy notice draft and the privacy plan inventory still say accounts and email are “not collected in MVP”, while the adopted free account design collects email-code, Google and Apple identity. The privacy page cannot be written from the older sentence. A bounded refresh of those two documents (or an explicit statement in T03 evidence of which text governs) must precede T03's legal pages.
| ID | Status | Evidence (2026-10-05) |
|---|---|---|
| D-L01 | Resolved by observation |
github.com/AlexandreZanata/brazil-fuel-prices returns HTTP 301 to https://github.com/AlexandreZanata/abastevo, which is public, MIT-licensed, default branch main; the repository description and website fields are empty. The canonical repository URL for the site is https://github.com/AlexandreZanata/abastevo. The local origin still uses the old name (works through the redirect; changing it is a separate local choice). The plan and ROADMAP are updated accordingly. |
| D-L02 | PENDING — maintainer confirmation | Public registry data shows abastevo.com.br registered on 2026-09-28 with Cloudflare name servers and no resolving address or web response at check time; the registrant is not disclosed. Ownership is not verified; the maintainer confirms whether it is theirs, or chooses another origin. This is not a trademark or availability clearance. |
| D-L03 | Criteria frozen, choice PENDING | See Hosting criteria. If D-L02 is the maintainer's domain on Cloudflare, Cloudflare Pages is the natural fit. |
| D-L04 | PENDING | Role mailbox or repository issue tracker. Needed before the legal pages and security.txt. |
| D-L05 | APPROVED 2026-10-05 | Wireframes and tokens reviewed and approved by maintainer. |
| D-L06 | Decided: default |
landing/ in this repository under the existing gate; separate repository only on explicit request. |
| D-L07 | PENDING (T04) | Default direction: normal crawlers allowed; AI-crawler policy recorded at T04. |
| D-L08 | PENDING (store publication) | Public listing URL and package identity after the app exists. |
Evaluate the chosen host against these before publication (document the verification at selection): custom response headers (security headers, preview X-Robots-Tag, per-path cache), redirects (HTTP→HTTPS, www→apex, trailing slash), real 404 status, automatic HTTPS, preview deployments, access-log privacy posture, cost/limits and rollback to a previous immutable artifact. Observation on 2026-10-05 from search summaries (re-verify at selection): GitHub Pages does not allow custom response headers (only in-document meta robots is possible); Cloudflare Pages and Netlify support a _headers file; Netlify marks its default deploy preview URLs noindex. The plan's artifact is host-neutral; only the headers/redirects source files depend on the choice.
Maintainer-reviewable static artifacts: 375 px wireframe and 1280 px wireframe. They are low-fidelity (structure, hierarchy, copy), generated as plain SVG with no script, font file, image or external reference, and are not the final visual style. Layout decisions captured there:
- Mobile: one column; header logo plus three anchor links in a row (no JS); hero, comparison cards stacked, three step cards stacked, optional profiles as a list, project block with privacy summary card, app card, FAQ as full-width disclosures, quiet footer.
- Desktop: content width about 60 rem (960 px); hero with the illustrative comparison beside the introduction; three columns for “Como funciona” and “Para quem é”; project block as two columns; app and FAQ side by side.
- One primary outline link (“Ver no GitHub”) and one plain-text store notice; no sticky bar, popup, carousel, autoplay, countdown or repeated download banner.
Frozen tokens (names are contract, final CSS names follow):
| Token | Value | Use |
|---|---|---|
--ink |
#0b1849 |
Headings, primary text (taken from the approved wordmark fill) |
--text-muted |
#44506b |
Body secondary text |
--link / --focus
|
#0042c5 |
Links, outline control, focus ring (3 px, 2 px offset) |
--brand-blue |
#0052f7 |
Non-text brand accents only |
--green-text |
#03664b |
ANP label text |
--surface |
#f5f8fc |
Alternate section background |
--footer-bg |
#eef2f9 |
Footer |
--tint-blue / --tint-green / --tint-amber
|
#e9f0ff / #e8f6ef / #fff3dc
|
Label pills (--ink or #7a4b00 text on amber) |
--line |
#c5cee0 decorative / #7b87a3 interactive boundary |
Card and control outlines |
| Type | System font stack; 16 px base, line height 1.6; H1 about 2–2.75 rem fluid; H2 1.5–1.75 rem; small 0.875 rem | No remote fonts |
| Spacing | 4 px base: 4, 8, 12, 16, 24, 32, 48, 64, 96 | Section padding 48–96 |
| Radius / shadow | 8 and 12 px, pill; no shadows except focus | Calm, flat |
| Breakpoints | 48 rem (three-column rows), 64 rem (two-column hero/project) | Plus 320 px minimum |
| Touch target | At least 44 × 44 CSS px | Links in header/footer get padding |
Contrast ratios computed from the WCAG relative-luminance formula on 2026-10-05:
| Foreground on background | Ratio | Target |
|---|---|---|
--ink on white / surface |
16.92 / 15.89 | AA text 4.5 |
--text-muted on white / surface / footer / blue tint / green tint |
8.06 / 7.57 / 7.18 / 7.05 / 7.24 | AA text 4.5 |
--link on white / surface / footer |
8.12 / 7.63 / 7.23 | AA text 4.5 |
--green-text on white / green tint |
6.99 / 6.27 | AA text 4.5 |
--link on blue tint |
7.11 | AA text 4.5 |
#7a4b00 on amber tint |
6.74 | AA text 4.5 |
--brand-blue on white (graphics) |
5.92 | Non-text 3 |
#7b87a3 interactive boundary on white |
3.60 | Non-text 3 |
#c5cee0 decorative outline on white |
1.58 | Decorative only; never the sole indicator of a control |
Dark appearance (fused Codex grayscale, owner-authorized 2026-10-11/12): the site follows the OS scheme with a header toggle and persisted choice; the navy wordmark is shown through a CSS presentation filter only in dark mode because no light-background wordmark variant exists. Measured dark pairs AA (body 19.08, muted 10.48, links 17.47, dark-text-on-button 16.13).
New-tab policy: store and GitHub CTA buttons open a new tab with
rel="noopener"; text and legal links keep same-tab navigation.
Composition reference: docs/assets/landing/redesign-20261011/landing-reference-v2.html
(authored HTML/CSS with unmodified app PNGs; the AI-generated concept is
superseded and excluded). It is a reference, not production markup.
Explicit supersessions of the P25 flat contract above:
| Old token | Revised value | Scope |
|---|---|---|
| Content width ~60 rem (960 px) | 1152 px max, 32 px gutters (measured from reference) | Desktop layout |
| System font stack | Manrope (headings/CTAs/nav/cards/prices, 700/800, 700 prices) + Source Sans 3 (prose/FAQ/legal, 400/500), self-hosted WOFF2, swap fallback (see Typography amendment) | Type |
| No shadows | One soft device-frame shadow only (0 16px 24px #0b184915); content cards stay flat |
Gallery/tutorial phone frames |
| 8/12 px radii | 16 px gallery cards, 20 px tutorial visual, 23–29 px device frames | Frames |
--text-muted #44506b, --surface #f5f8fc
|
Muted #53617b, pale #f4f7fc, line #dce3ee, teal #03664b (same as --green-text), red #df231b for tutorial overlays only |
Palette |
| H1 2–2.75 rem fluid | H1 56 px desktop / 32–40 px mobile, body 18 px, section H2 30–36 px (measured from reference; verify at LR10–LR12) | Scale |
Measured WCAG contrast (relative-luminance formula, 2026-10-11): navy on
white 16.92 / on pale 15.76; muted on white 6.24 / on pale 5.81; blue on
white 8.12; teal on white 6.99 / on pale 6.51 / on #edf6f2 6.34; white CTA
text on blue 8.12. All meet AA text 4.5. Red #df231b is never body text.
Logo provenance: brand SVGs under docs/assets/brand/ used verbatim (reference
209 px header / 145 px footer wordmark widths are measured, not new
artwork). Prototype deviations kept out of production: red focus ring and
tutorial overlay red stay prototype-only; production keeps the 3 px --link
focus ring. No phone mockup in the hero; device frames only in gallery and
tutorial sections. Wireframes wireframe-375.svg/wireframe-1280.svg remain
the approved low-fi structure; this revision changes style tokens, not layout.
Use only approved sources under docs/assets/brand/: logo SVG, wordmark SVG, app icon SVG and 1024 px icon PNG. T04 derives the favicon set (SVG, ICO, 180, 192, 512), site.webmanifest icons and the 1200×630 social image from them with recorded provenance; no new logo, lettering or illustration is created.
Required before T02 opens: D-L05 (maintainer reviews the wireframes, copy deck and tokens above) and confirmation of D-L02. Required before T03's legal pages: D-L04, the privacy-document refresh described above. Not required for T02: hosting choice (D-L03), crawler policy (D-L07), store listing (D-L08). No dates, traffic, costs or remote identifiers are invented.
Checks run for this docs-only task: local link and anchor check of this contract and the plan; SVG well-formedness and absence of script/image/external references in both wireframes; rendered-image inspection of both wireframes at their native widths; contrast computation as listed; character counts of title and description; repository, redirect, releases and registry observations dated above; git diff --check and scoped secret/private-data review. No browser acceptance, runtime or publication check is claimed.
LH04 synchronization (2026-10-12, explicit user instruction): adopt the text, GitHub/Google Play two-line action buttons and four-point hero strip from the local 8099 preview (landing-refresh df2b992). Keep LH01–LH03 authentic mockup, six illustrations, external source badges and grayscale theme. Header links remain accessible through a native disclosure when the action buttons occupy the header row. Prelaunch Play treatment is a non-link status; only the verified published build state may turn it into a store link. GitHub opens a separate tab with noopener and retains a usable accessible name at narrow widths.
The maintainer explicitly replaces the illustrative comparison in the opening with a professional responsive Android mockup using the real home capture. This supersedes the prior no-phone opening and illustrative comparison copy for this block only. B-BR-L01/L02 and BUC-L01/L02 remain: original app pixels, source/week context, explicit development status, no invented prices or live map claims. Generated cartography is decorative and labelled illustrative; ANP and community callouts remain semantic HTML. The existing source section continues to explain the distinction. Theme preference stores only light/dark locally, with system default and graceful storage-failure handling.
LH03 refinement (2026-10-12, explicit user instruction): replace dark navy/blue theme surfaces and accents with black/grayscale surfaces and prominent white text. Exactly one theme action icon is visible at any time on desktop/mobile. Regenerate the check/clock and contribution-camera artwork, then normalize solid ink and trace actual SVG geometry so alpha holes, dark smudges and blurred marks cannot appear in the final pictograms. Original PNG inputs remain documented.
LH02 refinement (same user session): the desktop artwork occupies the same grid row and exact height as the headline/description. Both semantic source badges sit below the artwork, outside the phone screen. Background uses an artistic Brazil silhouette with symbolic station lights, without asserting app coverage. Six generated-then-traced SVG pictograms illustrate consult/check/contribute and private driver/ride-hailing driver/small fleet cards; card text is retained.
The owner requests the warm illustrated landscape composition of the supplied reference: cream canvas, green emphasis, city, road, trees and sun around a real Android home mockup. Generate a separate text-free landscape and six minimal action/persona scenes, each with a unique dominant color (blue, green, orange, violet, teal and rose). Keep copy semantic HTML and real app pixels untouched; art is illustrative and never coverage or current price evidence. Keep existing prelaunch/store semantics and neutral dark mode. Preserve OpenCode changes at landing 41d1372: 12px gutters, revised brand scale, removed hero statistics and its 404 recovery header. Only hero/cards and necessary responsive styling are authorized. Ship responsive hash-named WebP derivatives with explicit dimensions, lazy card loading and verified hashes/size budgets; keep masters out of dist.
LH05 follow-up: the owner rejects a contained illustration block and requests an edge-to-edge, first-viewport hero using the supplied flat editorial landscape reference, with a 3840×2160 master/export and reusable matching trees, skyline, road and vehicle assets. The landscape belongs behind the whole hero, outside the content-width container. Preserve a readable left copy area, authentic phone, source/date disclosure, the completed six category scenes and OpenCode changes. The full-height opening supersedes the earlier equal copy/art-height constraint. Record generator-native dimensions separately from any 4K export dimensions.
The owner authorizes regenerating only the small-fleet illustration: a person actively organizing fuel costs beside a few vehicles, in the same soft 3D family as the other five cards and retaining the exclusive rose accent. The other five artworks remain byte-identical. The landscape remains full bleed, while header controls and hero foreground use the site's standard 72rem container and 12px gutters. Refine the device as an Android handset with a centered small punch-hole camera, subtle metal frame, narrow bezels and side controls; no iOS notch. Keep the authentic Android screenshot untouched, selecting at least the existing 720px derivative for a sharper display. Keep source badges outside the screen.
The owner explicitly rejects the illustrated hero background and authorizes a minimal professional opening instead. Remove the landscape from the homepage and emitted runtime art manifest; retain generated masters for later reuse. Use a clean neutral background, restrained geometric device support, balanced typography/spacing and the existing authentic Android mockup. Header/foreground keep the standard container. Preserve six card artworks, current buttons/copy, source/date disclosures, prelaunch status and black/grayscale dark mode. The latest instruction supersedes the LH05/LH06 landscape presentation requirements.
The owner requested a minimal, professional black/white presentation with one green accent, borderless tiles, pill controls and a single quiet primary action, applied to the landing and to the generated static portal pages. The owner then removed dark mode: the site ships a single light theme with no theme toggle, no dark palette and no theme script. This supersedes the LH01/LH07 dark-mode requirements. Existing copy contracts, six card artworks, the authentic Android mockup, source/date disclosures and prelaunch status are preserved.
The owner selected the Uber-style alternative as the main home: black top bar
and footer, an illustrated road/car/city hero with a working search hand-off
to /consultar/?uf=..&q=.., suggestion cards, a persona feature, a black
open-data band and the authentic app gallery followed by Android/GitHub
channels. The "O projeto" panel and the open-data map image were removed at the
owner's request; independence, MIT and no-tracking statements moved to the
footer. The real Android captures remain in the gallery instead of the hero.
This supersedes the LH06/LH07 hero device requirement.
LH09 follow-up (same day): the open-data band became a mirrored feature with the owner-supplied open-data scene (brief) and a three-item list. On desktop each feature's copy column, from title to buttons, matches the height of its art tile. The "Explore o que dá para fazer" cards then moved into a black band directly under the hero, with larger art, one short line each and an arrow; on phones they scroll horizontally with snap points.
Owner scope: replace the 1220 × 2712 gallery and tutorial captures with the
17 Nov 2026 Android captures under the
capture contract, finish every
published /como-usar/ chapter, add in-app steps to every guide and
calculator, and polish sections inside the LH08–LH10 style.
-
Gallery.
#aplicativoshows six 9:16 captures in product order: ANP weekly prices, community and ANP on a station page, route to a station, tank-fill cost, survey weeks, forum. The section head is the title alone (owner request, 2026-11-17) and never names an app version; source and week stay visible in the captures, their captions and alt text, and the capture date in the tutorials and guides. On phones it is one snapping row; no script, autoplay or carousel control. -
Derivatives. Only files listed in
landing/static/assets/app/provenance.jsonship: WebP at 360, 720 and 1080 px from the 1080 × 1920 masters with the recorded parameters, named<feature>-<NN-slug>-<width>w.webp. A 1080w file above the 120 KiB budget is not shipped. A derivative no page uses is removed with its entry. Captures markedemulatorArtifactorknownIssuein the manifest never ship. -
Chapters. A step quotes the exact pt-BR label and highlights the
control on the master pixels. A screen that cannot be shown (protected
against capture, emulator camera scene, known app defect) is a text-only
step (
textOnlyinlesson.json) that says why; nothing is mocked up. The sixteen published chapters areDisponível; unpublished ones keepEm breve/Planejadowithout a link. Chapter text never states a store listing. - Guides and calculators. Every guide has "Como fazer no aplicativo" (2–5 numbered steps, 2–4 captures, link to the chapter) and every calculator "No aplicativo". Wording follows the claim classes above: development status, dated ANP reference, community apart from ANP. Station ratings and comments stay "em breve" while the app keeps them behind its feature flag.
-
Home refinements (owner request, 2026-11-17). The heads of "Preços por
estado", "Guias populares", "Ferramentas" and the gallery are the title
alone, with no intro line. A secondary action is an outline button (1 px
--inkborder, no underline) beside the solid primary button. Guide and calculator cards are white with a 1 px--lineoutline: title, summary and an arrow at the foot, plus the category above the title where a list mixes categories (home, "Leia também", a calculator's related guides). The two feature art tiles are flat--surfacewith no gradient; from 80rem up they keep the LH09 equal height with the copy column, and between 64rem and 80rem they stay square. The Android and "Código disponível" cards lead with icon and title, then the description, then the actions, with no divider; the prelaunch store notice is a plain white status row, never styled as a button, and "Copiar link" is white with an ink outline. - Tutorial pages (owner request, 2026-11-17). On the hub, a published chapter is a white outlined card and the whole card is its link (one link per card, on the title); an unpublished chapter is a flat, quieter tile with no link, as B-BR-LH10-02 requires. Each card shows the TU number, the availability label, the title and the step summary. A chapter ends with two equal previous/next buttons, each a direction label over the chapter title, centred.
- Enlarged captures (owner request, 2026-11-17). With JavaScript, a click or Enter on any app capture (gallery, tutorial step, guide or calculator strip) opens it larger in a native modal dialog over a blurred, darkened page, with its alt text as caption. The close button, a click outside the capture or Escape closes it and returns focus. Without JavaScript the captures stay plain images; no dialog markup ships in HTML.
-
Hero art (owner request, 2026-11-17). The road, car, skyline and trees
scene of LH09 is replaced by one hand-authored SVG: the approved brand mark,
unchanged, on a dotted field with two route ribbons in the mark colours,
map pins and two abstract interface cards. It carries no text or numerals
and is decorative (
alt=""), never price or coverage evidence. Master and composing script:docs/assets/landing/hero-mark-20261117/. -
Hero search and tab icon (owner request, 2026-11-17). The two search
fields carry their icons in small white chips joined by a hairline. With
JavaScript the state field opens a listbox in the site style (UF badge and
name, keyboard and type-ahead support) instead of the native popup; the
native
selectstill holds the value and is the whole control without JavaScript. The browser tab icon is the bare brand mark, cropped to the mark so it renders larger: coloured for the light scheme (favicon.svg) and white/light grey for the dark scheme (favicon-dark.svg), chosen withmediaon the icon links. The.icoand PNG icons keep their white square for launchers. - Polish. Spacing, alignment, frames, hover/focus/pressed states and responsive fixes only. Tokens, fonts, brand, URLs, titles and structured data are unchanged; a chapter meta description changes only when the old one described the retired captures.
Scope: the user-requested presentation alignment of /privacidade/,
/excluir-conta/ and /termos/ with the current home and learning pages.
-
B-BR-L07-UI01: generate the three pages with the canonical home header
and footer, including branding, desktop navigation, native mobile menu,
consultation CTA and all footer groups. Nested home-section links use
/. - B-BR-L07-UI02: reuse the home color tokens, local fonts and shell, and the learning pages' readable article width, heading scale and spacing. Preserve legal copy, contact destinations, metadata and account behavior.
- BUC-L07-UI01: a reader opens any legal page from the footer, reads it on desktop or mobile and reaches the other public pages through the same navigation, including when JavaScript is unavailable.
- Acceptance: emitted header/footer parity with home, retained legal content and metadata, working home-section links, keyboard/native menu access and no horizontal overflow at 320, 390 and 1440 CSS pixels.
Owner scope: align /guias/ and /como-usar/ with the existing home and
consultation UI, then publish the static update to teste.abastevo.com.br.
The learning hubs and their existing detail routes inherit the home header,
footer, local fonts, neutral surfaces, spacing, buttons and keyboard focus.
-
B-BR-LH10-01: build learning chrome from the canonical home markup;
home-section links resolve through
/from every nested learning route. - B-BR-LH10-02: keep educational claims, formulas, sources, canonical URLs, tutorial chapters and availability statuses intact. Unpublished chapters remain noninteractive. No new feature, tracking or dependency.
- BUC-LH10-01: a reader opens either hub, chooses a guide/journey, follows a published chapter and uses the same navigation/footer on every learning route, including mobile and without JavaScript.
- Acceptance: header/footer parity, working local and home-section links, all 30 chapter entries/statuses, responsive cards/readable article widths, existing metadata/noindex/CSP and content tests.
- Delivery boundary: static landing files only, atomic release switch with the old release retained. Portal data, API/worker images, migrations, other namespaces and the production apex domain are outside this update.
- Home
- Roadmap
- docs-README
- docs-android-build
- docs-android-design-system
- docs-android-forum
- docs-android-games
- docs-android-map-engine
- docs-android-navigation
- docs-android-ocr-image
- docs-android-ocr-live-framing
- docs-android-premium-area
- docs-android-premium-integration
- docs-android-release
- docs-android-ui-containers
- docs-architecture-android-stack
- docs-architecture-android
- docs-architecture-backend
- docs-architecture-data-sources
- docs-architecture-overview
- docs-architecture-sources-ev-research
- docs-architecture-sources-national-limits
- docs-architecture-sources-national-stations
- docs-architecture-sources-register
- docs-assets-app-tutorial-CAPTURE_CONTRACT
- docs-assets-app-tutorial-FABLE_LANDING_POLISH_PROMPT
- docs-assets-app-tutorial-README
- docs-assets-attribution
- docs-assets-brand-README
- docs-assets-flags-ATTRIBUTION
- docs-assets-fuel-icons-README
- docs-assets-games-fuel-v1-README
- docs-assets-home-icons-README
- docs-assets-landing-fleet-android-20261012-BRIEF
- docs-assets-landing-hero-20261011-BRIEF
- docs-assets-landing-illustrated-20261012-BRIEF
- docs-assets-landing-illustrated-20261012-README
- docs-assets-landing-minimal-20261012-BRIEF
- docs-assets-landing-open-data-20261026-BRIEF
- docs-assets-landing-redesign-20261011-PREPARATION_EVIDENCE
- docs-assets-landing-redesign-20261011-README
- docs-assets-landing-redesign-20261011-REFERENCE_BRIEF
- docs-assets-landing-sync-20261012-BRIEF
- docs-assets-map-icons-README
- docs-backend-anp-ingestion
- docs-backend-api
- docs-backend-community-pricing
- docs-backend-data-model
- docs-backend-domain-model
- docs-backend-driver-private-data
- docs-backend-forum-architecture
- docs-backend-forum-bulletins
- docs-backend-forum-sources
- docs-backend-payments-provider-admission
- docs-backend-payments-provider-register
- docs-backend-photos-capture
- docs-backend-photos-subset-submission
- docs-backend-premium-api
- docs-backend-premium-cloud-protocol
- docs-backend-testing
- docs-backend-toolchain
- docs-brand-app-icons
- docs-brand-identity
- docs-decisions-001-kotlin-compose-stack
- docs-decisions-002-price-import-immutability
- docs-decisions-003-nominatim-reverse-geocode
- docs-decisions-005-modular-monolith-and-postgresql
- docs-decisions-006-official-catalog-and-exact-contracts
- docs-decisions-007-anonymous-proof-of-possession
- docs-decisions-008-privacy-and-retention
- docs-decisions-009-community-consensus-and-projections
- docs-decisions-010-private-object-evidence
- docs-decisions-012-licensing-and-hosted-business
- docs-decisions-015-kotlin-multiplatform-shared-domain
- docs-decisions-016-android-commercial-community-ios-deferred
- docs-decisions-017-station-profile-and-verified-representation
- docs-decisions-021-community-first-contribution
- docs-decisions-022-comaps-derived-native-map-engine
- docs-decisions-023-admin-suite-granted-tiers-contributors
- docs-decisions-025-private-abastevo-empresas-organization-boundary
- docs-decisions-026-multilingual-public-site
- docs-decisions-README
- docs-enterprise-README
- docs-enterprise-architecture
- docs-enterprise-backlog-INDEX
- docs-enterprise-backlog-ep00-governance
- docs-enterprise-backlog-ep01-platform
- docs-enterprise-backlog-ep02-organizations
- docs-enterprise-backlog-ep03-identity-access
- docs-enterprise-backlog-ep04-sync
- docs-enterprise-backlog-ep05-fleet-meters
- docs-enterprise-backlog-ep06-trips
- docs-enterprise-backlog-ep07-gps-navigation
- docs-enterprise-backlog-ep08-fuelings
- docs-enterprise-backlog-ep09-documents
- docs-enterprise-backlog-ep10-expenses-finance
- docs-enterprise-backlog-ep11-maintenance
- docs-enterprise-backlog-ep12-fuel-stock
- docs-enterprise-backlog-ep13-intelligence
- docs-enterprise-backlog-ep14-station-claims
- docs-enterprise-backlog-ep15-station-commerce
- docs-enterprise-backlog-ep16-subscriptions
- docs-enterprise-backlog-ep17-data
- docs-enterprise-backlog-ep18-imports-notifications-integrations
- docs-enterprise-backlog-ep19-back-office
- docs-enterprise-backlog-ep20-release
- docs-enterprise-business-rules
- docs-enterprise-contract
- docs-enterprise-conventions
- docs-enterprise-data-offering
- docs-enterprise-decisions
- docs-enterprise-domain-model
- docs-enterprise-glossary
- docs-enterprise-journeys
- docs-enterprise-modules-back-office
- docs-enterprise-modules-data
- docs-enterprise-modules-documents
- docs-enterprise-modules-expenses-finance
- docs-enterprise-modules-fleet
- docs-enterprise-modules-fuel-stock
- docs-enterprise-modules-fuelings
- docs-enterprise-modules-gps-navigation
- docs-enterprise-modules-identity
- docs-enterprise-modules-imports-notifications-integrations
- docs-enterprise-modules-intelligence
- docs-enterprise-modules-maintenance
- docs-enterprise-modules-organizations
- docs-enterprise-modules-station-claims
- docs-enterprise-modules-station-commerce
- docs-enterprise-modules-subscriptions
- docs-enterprise-modules-trips
- docs-enterprise-offline-sync
- docs-enterprise-permissions
- docs-enterprise-portal-routes
- docs-enterprise-privacy-security
- docs-enterprise-product-vision
- docs-enterprise-source-admission
- docs-enterprise-state-model
- docs-enterprise-testing
- docs-enterprise-ux-app
- docs-enterprise-ux-web
- docs-operations-README
- docs-operations-backup
- docs-operations-deploy-agent
- docs-operations-dou-editions
- docs-operations-edge-cache
- docs-operations-enterprise-activation
- docs-operations-map-static-overlay
- docs-operations-moderation-feedback
- docs-operations-moderation-profiles
- docs-operations-monitoring
- docs-operations-operator-access
- docs-operations-payments
- docs-operations-premium-billing
- docs-operations-recovery
- docs-operations-registry-daily-sync
- docs-operations-registry-runs
- docs-product-README
- docs-product-admin-tiers
- docs-product-community-community-first
- docs-product-community-experience
- docs-product-community-metrics
- docs-product-community-moderation
- docs-product-community-safety
- docs-product-community-terms-pt-br
- docs-product-driver-suite-README
- docs-product-driver-suite-android-state
- docs-product-driver-suite-cloud-sync
- docs-product-driver-suite-cost-profiles-and-maintenance
- docs-product-driver-suite-driver-model-and-earnings
- docs-product-driver-suite-foundation-decisions
- docs-product-driver-suite-gps-lifecycle
- docs-product-driver-suite-mobile-hub
- docs-product-driver-suite-odometer-review
- docs-product-driver-suite-outbox-wire
- docs-product-driver-suite-quick-refuel
- docs-product-driver-suite-reports
- docs-product-driver-suite-shifts-and-distance
- docs-product-driver-suite-signed-commands
- docs-product-ev-README
- docs-product-ev-charging-stop-planner
- docs-product-ev-energy-model
- docs-product-ev-financial-method
- docs-product-ev-journey-ui
- docs-product-ev-preparation
- docs-product-ev-typed-data
- docs-product-exploration
- docs-product-forum-contract
- docs-product-forum-policies
- docs-product-glossary
- docs-product-landing-content
- docs-product-landing-guides
- docs-product-landing-organic-growth-i18n-plan
- docs-product-licensing
- docs-product-map-discovery
- docs-product-map-favorites-and-trips
- docs-product-map-reports-routing-guidance
- docs-product-notification-content
- docs-product-official-prices
- docs-product-open-source-business
- docs-product-overview
- docs-product-payments-README
- docs-product-payments-offer-policy
- docs-product-premium-README
- docs-product-premium-financial-method
- docs-product-premium-source-policy
- docs-product-stations-catalog
- docs-product-stations-fuel-feedback
- docs-product-stations-fuel-quality
- docs-product-stations-identity-and-ev-catalog
- docs-product-stations-profile-contract
- docs-product-stations-profile-representation
- docs-product-stations-registry-sources
- docs-product-vehicle-registration
- docs-product-vehicles-and-occurrences
- docs-security-android-terms-acceptance
- docs-security-free-account-access
- docs-security-identity-profile
- docs-security-media-location-policy
- docs-security-privacy-notice
- docs-security-privacy-policy
- docs-security-retention
- docs-security-risks
- docs-security-security-privacy
- docs-store-README
- docs-store-play-readiness
- docs-store-play-store-listing
- docs-store-ugc-safety
Source: AlexandreZanata/Abastevo @ e4a67580fc368a59bc1c0f1e0466fc011313f330