Portfolio site migration
This site began as a static cloud-hosted website and evolved into a server-hosted deployment. The project involved domain configuration, DNS changes, EC2 provisioning, reverse proxy setup, SSL decisions, and practical troubleshooting across multiple layers.
What I practiced
- Cloudflare DNS and proxy configuration
- AWS EC2 setup and SSH access
- Nginx reverse proxy configuration
- Origin certificates and HTTPS troubleshooting
- Cache and browser behavior debugging
Static to dynamic hosting comparison
A useful learning exercise was comparing static hosting approaches with more traditional server-based deployment. This highlighted tradeoffs around speed, simplicity, caching, flexibility, and the operational differences between object storage hosting and a full Linux web server.
What I learned
- When static hosting is enough
- When a server-based Node deployment is more appropriate
- How reverse proxies fit into the request flow
- Why SSL mode and origin certificates matter
Support-focused documentation practice
Not every project has to be a big application. Documentation, repeatable steps, and clean technical communication are projects too. I use personal labs and deployment work to practice capturing what changed, what broke, what fixed it, and how to explain it clearly.
Why it matters
- Better repeatability
- Faster resolution next time
- Clearer handoffs between people
- Stronger support processes overall
Project goals going forward
I plan to continue expanding this portfolio with more practical examples. That includes cloud exercises, support workflow improvements, small automation ideas, infrastructure notes, and writeups that show how I think through technical issues.
Planned additions
- More detailed case studies
- Infrastructure notes and diagrams
- Support troubleshooting writeups
- Cloud learning summaries
- Documentation examples
What these projects represent
For me, projects are less about flashy demos and more about proof of process: can I set something up, troubleshoot it, secure it, document it, and explain why each choice matters? That is the kind of practical thinking I want this portfolio to reflect.