DEV Community

CrabPascal
CrabPascal

Posted on

Docs, Blog, and 2027: Closing the Loop | Docs, blog e 2027: fechando o ciclo

Bilingual post · Post bilíngue

Jump to: English · Português


English {#english}

Docs, Blog, and 2027: Closing the Loop

Series — Part 2 (finale): Previous: Changelog 2026: A Year of Sprints (060-changelog-2026-year-review). Maps: essentials/documentation-map, roadmap/squad, roadmap/review-360, essentials/project-status.

Sixty-one blog posts. Hundreds of Mintlify pages. Fourteen sprint releases in 2026. This finale connects the documentation site, the Dev.to campaign, and the 2027 horizon — so newcomers know where to land after Part 2 ends.

What we built in Part 2 (posts 032–061)

Part 1 (001–031) taught CrabPascal fundamentals: CLI, pipeline, sprints 1–13 themes, contributing.

Part 2 walked reorganized Mintlify docs:

  • Navigation and onboarding paths (032–033)
  • IDE, VS Code marketplace, Postman (034–036)
  • Architecture deep dives (037–040)
  • Sprint review series (041–048)
  • v2.22.0 and technical debt transparency (048–049)
  • Five-audit deep dive Lucas → Bruno → Helena → Marina → Rafael (050–054)
  • Education and migration (055–059)
  • Year wrap (060–061)

Each post links backward and carries doc_refs in meta.json — the blog is an index into docs, not a duplicate.

Mintlify: start here in 2027

essentials/documentation-map is the historical quick router. For current truth, prefer:

  1. essentials/project-status — v2.22.0 snapshot, what works, open gaps
  2. getting-started/leia-primeiro — three onboarding paths (user, contributor, auditor)
  3. roadmap/sprints-overview — next sprint targets
  4. technical-debt/backlog — living TD-IDs from audits

Archive pages (v1.5 status, old test reports) remain for history — do not treat them as current baseline.

Squad governance continues

roadmap/squad defines roles:

  • Rafael — release rhythm, IDE/CI/docs
  • Helena — architecture, RTL, Unicode, properties
  • Bruno — parser, semantic, execution
  • Marina — QA, fixtures, parity harness
  • Lucas — backend run/build, codegen

Every 2027 task must answer: Does this help real Delphi code compile, reduce run/build surprise, improve DX, or add a regression test?

Review 360° as north star

roadmap/review-360 remains the compatibility checklist. Blog posts translate sections for humans; the review is the engineer's spreadsheet. Update it when sprints close Priority 0 items.

Blog workflow going forward

Posts stay pending_review until you approve:

cd blog
node scripts/approve.mjs 061-year-end-docs-blog-2027
npm run publish:draft -- 061-year-end-docs-blog-2027   # optional preview
npm run publish -- 061-year-end-docs-blog-2027 --publish  # when ready
Enter fullscreen mode Exit fullscreen mode

Phase 3 planning (2027) might shift to release notes + shorter devlogs — but the bilingual pattern stays: English and Português in one Dev.to article.

2027 priorities (inferred from status + audits)

Area Direction
Codegen parity Properties, methods, exceptions (real lowering)
IDE Problems panel, correct build command
RTL IO encoding, generics enumerators
QA run/build parity suites, offline Horse smoke
Docs Sync test README, reduce version drift

Sprint 15+ entries in sprints-overview will name owners — watch kickoff posts for details.

Thank you / loop closed

If you read from post 001 to 061, you traced CrabPascal from hello world to technical audit honesty. The loop closes where it opened: real Pascal code on your machine.

git clone https://bitbucket.org/alphatecnologia/crabpascal.git
cd crabpascal
cargo build --release
crab-pascal run examples/crud/crud.dpr
Enter fullscreen mode Exit fullscreen mode

Then open Mintlify locally or browse docs when hosted — paths in doc_refs match mintlify/ folder structure.

Stay connected

Part 2 complete. Part 3 awaits your roadmap choices in 2027.


Português {#portugus}

Docs, blog e 2027: fechando o ciclo

Série — Parte 2 (finale): Anterior: Changelog 2026: um ano de sprints (060-changelog-2026-year-review). Mapas: essentials/documentation-map, roadmap/squad, roadmap/review-360, essentials/project-status.

Sessenta e um posts de blog. Centenas de páginas Mintlify. Quatorze releases sprint em 2026. Este finale conecta site de documentação, campanha Dev.to e horizonte 2027 — para newcomers saberem onde pousar após Parte 2 terminar.

O que construímos na Parte 2 (posts 032–061)

Parte 1 (001–031) ensinou fundamentos CrabPascal: CLI, pipeline, temas sprints 1–13, contribuição.

Parte 2 percorreu docs Mintlify reorganizados:

  • Navegação e trilhas onboarding (032–033)
  • IDE, marketplace VS Code, Postman (034–036)
  • Deep dives arquitetura (037–040)
  • Série sprint reviews (041–048)
  • v2.22.0 e transparência débito técnico (048–049)
  • Deep dive cinco auditorias Lucas → Bruno → Helena → Marina → Rafael (050–054)
  • Educação e migração (055–059)
  • Wrap-up anual (060–061)

Cada post liga para trás e carrega doc_refs no meta.json — o blog é índice para docs, não duplicata.

Mintlify: comece aqui em 2027

essentials/documentation-map é roteador rápido histórico. Para verdade atual, prefira:

  1. essentials/project-status — snapshot v2.22.0, o que funciona, gaps abertos
  2. getting-started/leia-primeiro — três trilhas (usuário, contribuidor, auditor)
  3. roadmap/sprints-overview — alvos próximo sprint
  4. technical-debt/backlog — TD-IDs vivos das auditorias

Páginas arquivo (status v1.5, relatórios teste antigos) permanecem como histórico — não trate como baseline atual.

Governança squad continua

roadmap/squad define papéis:

  • Rafael — ritmo release, IDE/CI/docs
  • Helena — arquitetura, RTL, Unicode, properties
  • Bruno — parser, semântica, execução
  • Marina — QA, fixtures, harness paridade
  • Lucas — backend run/build, codegen

Toda tarefa 2027 deve responder: Isso ajuda código Delphi real a compilar, reduz surpresa run/build, melhora DX ou adiciona teste de regressão?

Review 360° como north star

roadmap/review-360 permanece checklist de compatibilidade. Posts blog traduzem seções para humanos; review é planilha do engenheiro. Atualize quando sprints fecharem itens Prioridade 0.

Workflow blog daqui pra frente

Posts ficam pending_review até você aprovar:

cd blog
node scripts/approve.mjs 061-year-end-docs-blog-2027
npm run publish:draft -- 061-year-end-docs-blog-2027   # preview opcional
npm run publish -- 061-year-end-docs-blog-2027 --publish  # quando pronto
Enter fullscreen mode Exit fullscreen mode

Planejamento Fase 3 (2027) pode shift para release notes + devlogs curtos — mas padrão bilíngue permanece: English e Português no mesmo artigo Dev.to.

Prioridades 2027 (inferidas de status + auditorias)

Área Direção
Paridade codegen Properties, métodos, exceptions (lowering real)
IDE Painel Problems, comando build correto
RTL IO encoding, enumerators generics
QA Suítes paridade run/build, smoke Horse offline
Docs Sync README testes, reduzir drift versão

Entradas Sprint 15+ em sprints-overview nomearão donos — watch posts kickoff para detalhes.

Obrigado / ciclo fechado

Se leu do post 001 ao 061, traceou CrabPascal de hello world até honestidade de auditoria técnica. O ciclo fecha onde abriu: código Pascal real na sua máquina.

git clone https://bitbucket.org/alphatecnologia/crabpascal.git
cd crabpascal
cargo build --release
crab-pascal run examples/crud/crud.dpr
Enter fullscreen mode Exit fullscreen mode

Depois abra Mintlify local ou browse docs quando hosted — paths em doc_refs batem com estrutura pasta mintlify/.

Fique conectado

Parte 2 completa. Parte 3 aguarda suas escolhas de roadmap em 2027.


Published on dev.to/@crabpascal · Código em CrabPascal

Top comments (0)