Website Studio

Website Studio started with a practical goal: I wanted to build and manage my own personal website. I could have used an existing CMS or website builder, but I wanted real control over how my projects, articles and professional services are presented, and the freedom to extend the site as new ideas came up, without being boxed in by someone else's structure. So I built my own.

What started as the backend for a personal website gradually became something more useful: a Studio for managing everything behind the public site, not just its pages. The website was still the starting point, but the capabilities I kept adding turned out to be useful well beyond any single page, and made running the website itself much easier.

More than publishing

The first requirements were simple: a place for my profile, technical articles,engineering projects and contact information. From there the bar kept rising. Projects needed to read as real case studies, not static pages. Articles needed to support different technical topics and formats. Media needed to be reusable across both. And publishing something new should never mean editing templates or source code.

Preparing my Group DevOps Mentorship and other professional services added another dimension entirely. The website couldn't just explain what I offer, it had to let people get in touch, apply for an offering, and move through the steps that come before we actually start working together. Website Studio grew to meet that, and became the place where I manage both the website's content and the activity happening around it.

One place to manage the website

The public website and Website Studio serve two different purposes. Visitors see the finished result: my projects, articles, professional offerings and information about my work. Website Studio is where I manage what sits behind that public experience. Instead of treating every content change as a development task, I work with the content directly in the Studio and decide what gets published.

From one place, I prepare and publish articles, maintain project case studies, manage media, update professional offerings and handle incoming requests. That separation has become more useful as the website has grown: the public site stays focused on presenting information clearly, while the work of maintaining it happens on its own, in the Studio.

From personal website to working platform

The biggest change came when the website moved beyond presenting my work and started supporting real professional services. My Group DevOps Mentorship is one example. The website presents the mentorship, gives someone the information they need before applying, receives applications, and supports the commercial steps required before the mentorship actually begins. External services such as email and payment providers connect in where they're needed, while I keep managing the overall process through Website Studio.

That's the point where I stopped thinking of Website Studio as just the administration area of my personal website. The public website became one use of a larger system I can keep extending as my work develops. Publishing is still a core part of it, but Website Studio now also supports the professional activity that happens around what I publish and what I offer.

Built and operated by me

Website Studio is a project where several areas of my work come together. I develop the application with Django, operate the infrastructure behind it, manage deployment and configuration, integrate external services, and keep extending the system as new requirements appear. That means I can follow a feature from the first idea through implementation and deployment, until I'm actually using it myself.

That's one of the reasons I enjoy working on it. It isn't a portfolio project I finished once and left alone. It's software I actively use to run my own website, so improvements have a practical purpose, and new capabilities exist because I actually needed them.

The website is the demo

The clearest demonstration of Website Studio is the website you're using right now. The Projects section where this case study lives, the Articles area, my professional offerings, and the ways visitors can reach me are all managed through the same system. Instead of building a separate, artificial demo for my portfolio, I can show Website Studio through the real website it powers.

The Studio itself isn't publicly accessible, but selected screenshots and short walkthroughs can show how I manage the website behind the scenes, without exposing private administration or sensitive information. That lets me demonstrate both sides of the project: the public experience visitors interact with, and the Studio I use to operate it.

Current focus

Website Studio is still evolving. Right now my focus is making the platform commercially operational for my own mentorship offering, continuing to improve the publishing experience, and preparing the next stage, where Website Studio can eventually support more than one user and website.

The goal isn't to reproduce every feature of an existing CMS or website builder. I want Website Studio to stay focused on what I actually need: publishing my engineering work, presenting professional services, and operating the activity around them. My personal website started the project, but it's increasingly becoming the first working example of what Website Studio itself can become.