Ayan Mamun
Contact

Typed content layer v1 for archive and project data

Release v1 introduces a typed content layer for archive and project modules to improve maintainability and reuse.

Share

The new typed content layer separates domain content from rendering logic. This keeps routes thin and predictable.

What changed

Shared interfaces now define structure for archive entries, project cards, and profile modules.

Page-level components consume typed content sources instead of embedded literal data.

Compatibility

The release is backward compatible for existing routes.

Future updates can add fields incrementally with explicit type-level migration.