Personal Website

A professional home for engineering work, shipped projects, media, and photography.

Built to present serious work clearly, with enough structure underneath to support content updates, private administration, and API-backed integrations over time.

Selected Projects Open Resume Deployment Test

louisbeer.net• api.louisbeer.net• admin.louisbeer.net

Positioning: Engineer, builder, and creative technologist
Domain structure: Public site, admin surface, and API split cleanly by subdomain
Current state: Production-ready shell awaiting final portfolio content

Site Intent

Ready for public work now and operational growth later.

This shell already runs in production conditions and is structured to absorb real content without reshaping the site architecture.

Traffic target Structured for 1,000+ monthly visits

Deployment Oracle VPS and subdomain ready

Stack PHP, HTML, CSS, JS, TS

Admin posture Session auth, timeout, rate limiting

Selected Areas

Core sections are prepared for real material and public-facing links.

The structure is ready for case studies, resume details, coding work, content links, and photography collections without requiring a rewrite later.

Portfolio-ready project system Case-study cards, reusable content data, and API output all derive from one source of truth. Operational separation by domain Public site, private admin surface, and API endpoint paths are prepared for dedicated subdomains. Media and photography sections Content creation work and photo libraries have page-level structure ready for real assets and publishing. Resume Ready for production content and public-facing links. Content Creation Ready for production content and public-facing links. Contact Ready for production content and public-facing links.

Portfolio Shape

A stronger first pass at how the finished site should read.

This section gives the homepage a clearer editorial spine instead of reading like a generic landing page.

Selected projects

Use this area to present 3-6 real case studies with context, role, constraints, stack, and outcome. Open section

Engineering depth

Reserve this section for code repositories, architecture narratives, and technical decision-making. Open section

Public-facing work

Keep media, content, and photography adjacent to the technical portfolio without mixing their purposes. Open section

Approach

Designed to hold up once real information is added.

Clear presentation

The public-facing surface stays readable, restrained, and content-first.

Low-friction upkeep

Simple PHP rendering keeps maintenance practical on a small VPS.

Expansion paths

Admin and API boundaries are already defined for future workflows.

Production Readiness

The infrastructure work is largely done.

DNS, TLS, Nginx, PHP-FPM, and GitHub Actions deployment are already wired for the live Oracle VPS.
The site structure is centralized in shared content config so replacing placeholder text does not require touching templates.
The remaining work is portfolio substance: resume detail, project narratives, links, and real media assets.