A readable front door with publishing and operational boundaries behind it.
A portfolio should make evidence easy to find without turning a hiring conversation into a software demo. Publishing, external feeds and optional AI still need meaningful boundaries.
The workflow below follows the main handoffs and the boundaries each one introduces.
Reviewed project records and repository-backed writing supply ordinary routes.
Next.js renders the core pages, and links remain useful without optional services.
The Project Advisor selects reviewed questions, then proposes a plan from submitted input. An opt-in state demo illustrates a separate workflow.
Authenticated publishing, health checks and private persistence remain behind server boundaries.
The current Advisor asks reviewed questions before drafting a proposal. The earlier evidence finder is retired from the interface; its guarded, default-off endpoint remains separate infrastructure.
The alternative. An open-ended portfolio chatbot could produce fluent answers with unsupported experience or claims.
Server-render the content and label local simulations and disconnected integrations.
The alternative. Making a database or AI session mandatory would make the simplest visitor journey the most fragile one.
Replace presentation while retaining authenticated publishing, sanitized Markdown and operational APIs.
The alternative. A visual rewrite alone would be smaller and would discard useful production behavior.
These are the failure cases and maintenance responsibilities that shape the implementation:
Data paths, service boundaries and fallback behavior.
The retained publishing, content and operations API contract.
Want to discuss the details? Let’s talk ↗