Roadmap

Overview

This portfolio is intended to evolve alongside my career rather than remain a static showcase. The current implementation establishes the foundation for a broader engineering platform that will continue to grow as I explore new technologies, solve new problems and complete additional projects.

The roadmap below represents the direction of the project rather than a fixed schedule. Priorities will naturally evolve as the platform matures and new opportunities arise.

---

Application Platform

The current implementation focuses on a single Next.js application. Future development will introduce additional backend services to separate responsibilities and support richer functionality.

Planned improvements include:

• A FastAPI backend providing APIs and background services.
• Shared packages and reusable libraries within the existing monorepo.
• Improved server-side data processing and scheduled tasks.
• Additional portfolio applications sharing the same platform.

---

Cloud Infrastructure

The AWS environment has been designed with future expansion in mind.

Planned infrastructure improvements include:

• A fully independent production environment.
• Private application services running within the existing private subnet architecture.
• Expanded monitoring, observability and operational dashboards.
• Continued refinement of networking and deployment automation.

---

Engineering Practices

As the platform grows, I intend to continue improving the engineering practices surrounding the application rather than focusing solely on new features.

Areas of ongoing improvement include:

• Expanded automated testing.
• Performance profiling and optimisation.
• Improved deployment validation and rollback strategies.
• Continued refinement of documentation and architecture diagrams.

---

Integrations

One of the longer-term goals of the project is to expose live information rather than relying solely on static content.

Future integrations include:

• GitHub repository and workflow data.
• AWS infrastructure and deployment status.
• Additional third-party APIs that demonstrate practical backend integration patterns.

---

Documentation

The documentation is intended to evolve alongside the platform.

Future improvements include:

• Expanded engineering notes for each major subsystem.
• Additional architecture and networking diagrams.
• Operational documentation covering deployment, troubleshooting and lessons learned.
• New chapters documenting future projects and platform capabilities.

---

Long-Term Vision

The long-term goal is for this portfolio to become more than a personal website.

I want it to serve as a continually evolving engineering platform that demonstrates not only completed projects, but also the thought process, trade-offs and technologies involved in designing, deploying and maintaining modern cloud applications.

Rather than rebuilding the portfolio every few years, the intention is to continue extending the same platform as my experience grows, allowing the documentation and architecture to evolve alongside it.