I designed and built my engineering portfolio and Foundry, its administration platform, with AI-assisted design and development. Foundry keeps portfolio content and resume generation connected to one content workflow, with theme previews, publishing, analytics, skill search, and an AI assistant.
Updating a portfolio and a separate resume can leave conflicting versions of the same experience. I wanted a personal engineering platform where I could update content on the go and help visitors find evidence relevant to a role.
PostgreSQL stores managed content and revisions. A typed JSON snapshot feeds the public Next.js build and resume generation. Foundry provides authenticated editing, theme management and previews, and a publishing integration with Vercel.
- 01Foundry editing
- 02PostgreSQL content
- 03Typed build snapshot
- 04Portfolio and resumes
PostgreSQL is the managed content store; typed JSON is its build-time projection rather than a second independently maintained source.
Build-time content separates public rendering from live CMS reads, but saved changes must be published before visitors see them. Maintaining a custom editor and publishing workflow also creates maintenance work that a hosted CMS would otherwise handle.
Product and engineering ownership
The design concept, local JSON data approach, PostgreSQL storage, authentication, theme previews and management, publishing, resume variants, and analytics dashboard were my decisions. I was the sole designer and developer, using Figma Make for design and Cursor and Codex for implementation assistance. This demonstrates end-to-end ownership, not management of a team.
One content workflow
Foundry is intended to keep my portfolio and resumes current from one source. The public site includes skill-based search so visitors can check role relevance, plus an AI assistant for questions about my work. Resume selection rules remain explicit and should be reviewed when the underlying content changes.
Deployment and operations
I deploy through Git to Vercel, manage deployment secrets there, and use PostgreSQL as the database. Cloudflare manages the domain. I use Vercel Analytics, Speed Insights, and Observability, with analytics presented in Foundry. These operating responsibilities are owner-confirmed; no uptime or incident-recovery claim is made.
A dated performance result
The supplied PageSpeed report, captured October 1, 2026 at 01:15 GMT+6 with Lighthouse 13.5.0, shows homepage Performance of 100 on desktop and 94 on mobile. Accessibility, Best Practices, and SEO each score 100 on both. The mobile test emulates a Moto G Power on Slow 4G. The report shows no real-user field data, so these lab results do not establish site-wide or real-user performance. Source: https://pagespeed.web.dev/analysis/https-sakibashraf-dev/2q70qltn1q?form_factor=desktop