17
Portfolio · technical journal
Sorune Personal Web
An interconnected portfolio and technical journal with independent content, theme and deployment boundaries.
Public websites running · manually curated catalogue
- Period
- 2026 — present
- Role
- Web and editorial system developer
PROJECT / DECISION RECORD
From the problem to the implementation
- 01Problem
Disconnected project cases and engineering articles obscure both outcomes and decisions.
- 02Design decision
Separate Next.js portfolio, Ghost theme, canonical articles and deployment infrastructure.
- 03Implementation
Linked work, writing and evidence with responsive live acceptance and Figma design records.
Problem
17Disconnected project cases and engineering articles obscure both outcomes and decisions.
Constraints
- Keep private operations private and separate Ghost content authority from theme presentation.
- Ghost editorial state and portfolio case descriptions have different owners.
- Do not expose private service addresses or non-public repository credentials.
Engineering decisions
- Separate Next.js portfolio, Ghost theme, canonical articles and deployment infrastructure.
- Keep article source in blog-content and presentation in ghost-theme.
- Derive featured and full lists from one catalogue and link only public evidence.
Implementation
- Linked work, writing and evidence with responsive live acceptance and Figma design records.
- Deploy separate Next.js portfolio and Ghost journal with bidirectional project/article navigation.
- Record deployment revisions and scoped responsive checks in History.
Verification / evidence
Source evidenceObserved
Portfolio, Ghost theme/content/deployment repositories and live acceptance records are available.
Result / current state
Public portfolio and blog are deployed; PaaS-driven catalogue sync remains deferred.
Current statusPublic websites running · manually curated catalogue