6
published cases
Portfolio
Overview
This page organizes the portfolio as a delivery system: cases, stacks, capabilities and delivery models appear connected so the reading stays easy to filter, inspect and maintain.
Current snapshot
Portfolio snapshot
6 cases, 5 domains and 4 delivery modes.
Data from this page is also available in /data/site-portfolio.json, /data/site-projects.json, /data/site-capabilities.json, /api/portfolio?lang=en-US, /api/projects?lang=en-US and /api/capabilities?lang=en-US.
Read by category
For thematic views by delivery category, use Categories.
Read by project dossier
For per-case navigation with technical and operational context, use Projects.
Read by stack
For recurring technologies and deep stack dossiers, use Stacks.
Cases
Live portfolio
Cases, stacks and delivery signals in a filterable layer.
This portfolio organizes product, docs, platform, automation and public presence without breaking maintenance simplicity.
6
featured entries
6
results in current filter
SaaS platform
application · activenode-next
Nx environment with Next apps, cross-app contracts, smoke tests and a Docker-based development stack.
Focus
- SaaS product
- cross-app contracts
- full stack experience
Outcomes
- standardized dev environment
- navigation tests
- platform readiness
Editorial engine
docs · activenode-vitepress
Institutional and technical site in VitePress with a shared catalog, public exports and an auditable API.
Focus
- data-driven content
- static publishing
- discoverability
Outcomes
- reusable central catalog
- public JSON exports
- modular searchable theme
UI library and Storybook
docs · activenode-web-components
Public Web Components library with Storybook, multiframe wrappers and auditable npm distribution.
Focus
- reusable components
- public showcase
- auditable release flow
Outcomes
- public Storybook
- accessible npm package
- typed central catalog
Main website
brand · activemozg.com.br
Professional positioning, portfolio and editorial layer of the lab on its own domain.
Focus
- technical presence
- editorial narrative
- public portfolio
Outcomes
- consistent own domain
- institutional distribution
- base for continuous evolution
Complementary portal
brand · evolvingmozgbrasil.github.io
Complementary public layer for professional presentation, portfolio and link distribution across channels and projects.
Focus
- professional presentation
- supporting landing
- link distribution
Outcomes
- presence amplification
- channel hub
- living portfolio
Technical profile
docs · activegithub-profile
Lean summary of specialty, portfolio and public links for GitHub surfaces.
Focus
- technical identity
- quick specialty context
- public surface area
Outcomes
- clearer profile
- coherent public links
- lean editorial distribution
Capabilities
Capabilities
Matrix of domains, technologies and delivery modes.
This slice translates the portfolio into operational capability and makes clear how delivery connects to stack, docs and readiness.
Recurring technologies
Tools that show up consistently across delivery modes.
Domain
Architecture and contracts
Domain modeling, predictable envelopes, auditable routes and structures ready for safe evolution.
Practices- small and clear contracts
- explicit payloads
- low-friction versioning
Domain
Full stack product
Web experiences, reusable components, front and back integrations and operational docs moving together.
Practices- content-driven UI
- searchable flows
- components with simple maintenance
Domain
Platform engineering
Repeatable local environments, matrix CI, infrastructure as product and technical readiness per project.
Practices- local Docker
- validation matrix
- documented runtime standard
Domain
Observability and operations
Health checks, request IDs, static exports, operational snapshots and real verification triggers.
Practices- quality gates
- health endpoints
- public artifacts for auditability
Domain
Automation and AI ops
Local pipelines, assisted automations, execution guardrails and the combination of data, runtime and operations.
Practices- multimodal pipelines
- operational guardrails
- local assistance with context
Delivery mode
Structured diagnosis and refactor
Legacy reading, contract consolidation, architecture cleanup and a green pipeline at the end.
Best suited for- bases with technical drift
- sites and apps without a clear standard
- growing systems
Delivery mode
Portfolio and public surfaces
Sites, portals, technical profiles and editorial layers with coherent distribution and strong readability.
Best suited for- technical brand
- public presence
- content with SEO and discoverability
Delivery mode
Auditable minimal API
Small HTTP layers with clear envelopes, filters and data suited for automation and troubleshooting.
Best suited for- lightweight BFFs
- operations with visibility
- future integrations
Delivery mode
Platform readiness
Per-project quality, operational scripts, containerized build and alignment between docs and runtime.
Best suited for- local pipelines
- small teams
- evolution with a strict standard