70 docs tagged with "portfolio"

Governance for CI/CD and environment promotion features.

Governance for core page features and the primary reviewer flow.

Governance for features that integrate documentation and evidence workflows.

Checklist for validating that portfolio claims map to verifiable artifacts across code and documentation.

Governance for registry-driven content and evidence components.

Governance and index for portfolio-app feature documentation.

Vercel Web Analytics and performance monitoring.

Scroll-aware back-to-top control with reduced-motion support.

CI enforcement of bundle size thresholds.

Lint, format, typecheck, and audit gates enforced in CI.

Public-safe contact page with static links only.

Evidence-first CV timeline with proof links and reviewer guidance.

Playwright E2E coverage for routes, links, and metadata.

Environment-safe construction of evidence and repository links.

Direct links from the app to dossiers, ADRs, and runbooks.

Evidence badges and grids that surface documentation artifacts.

Health and status endpoint for operational visibility.

Incremental static regeneration and cache-control behavior.

Landing page with evaluation path, evidence callouts, and key entry points.

Shared section and callout components for consistent page structure.

Single-command local verification for quality and tests.

Global metadata for SEO and social previews.

Sticky navigation with desktop links and mobile menu.

Automatic PR preview environments for validation.

Required checks and deployment checks before production.

Evidence-rich project detail pages with badges and verification checklist.

Data-driven project registry with schema validation and slug guarantees.

Featured and all-projects gallery backed by the registry.

Respects user motion preferences across animations and transitions.

Explicit guidance to lead reviewers to the evidence trail.

Git revert based rollback for production issues.

Intersection Observer based fade-in transitions for content blocks.

Public-safe configuration and secrets scanning discipline.

OWASP-aligned security headers and CSP enforcement.

Manual staging validation before production promotion.

Schema.org Person and Website structured data for search engines.

Dependabot, CodeQL, and audit gates for dependencies.

Pre-hydration script to prevent flash of incorrect theme.

CSS variable theme system with light/dark tokens and transitions.

Class-based light and dark theme toggle with persistence.

Vitest-based unit tests for registry, APIs, components, and pages.

Explicit, public-safe constraints and intentional omissions for the portfolio program.

Governance for navigation, motion, and UX refinement features.

Governance for performance, caching, and observability features.

Phase 4 completion release note covering observability, security hardening, runbooks, and UX/SEO documentation upgrades.

Architecture of the Portfolio App: Next.js boundaries, content model, evidence-link strategy, and scalability patterns.

Guided tour of portfolio-app features sourced from roadmap, ADRs, runbooks, and implementation.

Operational posture for the Portfolio App: deploy/rollback expectations, maintenance cadence, and recovery assumptions for a public portfolio service.

What the Portfolio App is, what it must prove, and how it will be evaluated by enterprise reviewers.

Security posture for the Portfolio App: threat surface, enforceable SDLC controls, and public-safe content and deployment practices.

Rules for deprecating and archiving portfolio content while preserving evidence integrity.

Governance checklist for adding new portfolio content or making major changes.

What the Portfolio Docs App is, why it exists, and what it proves — plus the minimum viable enterprise outcomes and evidence expectations.

How to use this Docusaurus repository as an enterprise-grade, docs-as-code evidence system for the portfolio web app and linked demo projects.

Rules for what belongs in the portfolio and the minimum evidence required for inclusion.

Curated, recruiter-friendly documentation that frames the portfolio as a product and links to deeper technical evidence across architecture, DevOps, security, and operations.

Phase 5 kickoff release note covering reviewer guidance, evidence validation, and v1.0 freeze preparation.

Phase 6 release note establishing long-term governance, versioning, and archival policies.

Chronological record of portfolio program releases with auditable summaries of changes, governance updates, and operational impacts.

Release note covering security hardening across the Portfolio Docs App and Portfolio App, including CSP headers, audit gates, and governance updates.

Final Phase 5 release note marking the v1.0 freeze and reviewer-ready portfolio state.

Semantic versioning rules and release expectations for the portfolio program.

Enterprise-style roadmap for building the Portfolio App (Next.js/TypeScript) and its supporting evidence ecosystem (Docusaurus), with phased deliverables and governance artifacts.

Enterprise-grade TypeScript portfolio web application (Next.js) serving as an interactive CV and a platform to showcase verified project evidence.

Standardized, repeatable project documentation packages for the portfolio app and each demo project, organized for fast review and deep technical validation.

A fast, evidence-first path to validate the portfolio in under 15 minutes.

Governance for security-related features and controls.

Governance for SEO, social metadata, and structured data features.

Governance for testing strategy and quality gate features.

Governance for theming, accessibility, and motion preferences.