Professional Portfolio
Responsive pages present my background, skills, projects, certifications, CV, contact information, and professional development.
Loading...
Please wait while the page loads.A production-deployed cybersecurity portfolio and community platform combining professional content, authentication, role-based access, blogging, moderation, monitoring, backups, and an operational private-cloud Drive gateway.
Project Overview
What began as a personal portfolio developed into a broader production platform. It now demonstrates web development, secure authentication, application architecture, infrastructure integration, operational monitoring, and long-term technical maintenance.
Create a professional platform for cybersecurity projects, qualifications, skills, and technical writing
Build secure authentication, profiles, and role-based access
Support blogging, community interaction, administration, and moderation
Provide a secure, role-authorised gateway to the self-hosted private-cloud service
Operate the platform with monitoring, backups, security controls, and documented maintenance
Platform Capabilities
The application combines public professional content with authenticated community features, protected management tools, and operational infrastructure.
Responsive pages present my background, skills, projects, certifications, CV, contact information, and professional development.
Supabase authentication supports registration, sign-in, password recovery, user profiles, account settings, and public profile pages.
The platform includes articles, categories, tags, saved posts, reactions, comments, notifications, related content, and reading features.
Protected interfaces support post management, user administration, comment review, appeals, restrictions, and content moderation.
The drive.meetshawon.com subdomain provides authenticated, role-authorised access to the operational self-hosted TrueNAS and Nextcloud service.
The contact workflow uses server-side validation, Cloudflare Turnstile, Resend, controlled error handling, and a verified custom-domain sender.
Architecture
The platform separates domain management, hosting, application logic, backend services, and operational tooling into clear layers.
Manages DNS for meetshawon.com and drive.meetshawon.com while supporting the wider domain and email-routing configuration.
Builds and hosts the production Next.js application, manages deployments, custom domains, runtime logs, and observability.
Provides App Router pages, server and client components, APIs, metadata, proxy routing, security headers, and application logic.
Provides authentication, PostgreSQL data, user profiles, role information, Storage, and application access controls.
Sentry, UptimeRobot, Resend, GitHub security tooling, and backup routines support reliability and ongoing maintenance.
Security Engineering
Security is treated as part of application design, deployment, repository management, and ongoing operations rather than as a final visual feature.
Protected routes verify the authenticated user on the server instead of relying only on browser state.
Administrative, moderation, and Drive functionality is restricted according to profile roles and server-side authorisation checks.
Content Security Policy, frame protection, content-type protection, referrer rules, permissions restrictions, and HTTPS upgrading reduce browser-side risk.
Cloudflare Turnstile, validation, controlled error responses, and limited logging protect the public contact endpoint.
Dependabot, CodeQL, Secret Protection, Push Protection, npm audit, and controlled dependency updates support repository security.
Supabase database and Storage backups are created through documented CLI procedures and kept outside the Git repository.
Operations
Production readiness includes visibility into application errors, uptime, deployments, backend services, dependencies, and recovery procedures.
Captures production exceptions, stack traces, performance information, logs, and error notifications.
Monitors the application health endpoint and provides failure and recovery alerts.
Reports and service logs provide visibility across authentication, database, API, Storage, and Realtime services.
Dependency, code-scanning, secret, and push-protection controls monitor the source repository.
Problem Solving
Several production issues required investigation across routing, authentication, deployment, monitoring, backup, and code quality.
Challenge
The Drive subdomain originally failed to reach the intended application route.
Solution
Hostname-aware proxy routing was implemented and the Next.js 16 proxy convention was applied correctly.
Challenge
Users entering through the Drive subdomain needed to authenticate on the main domain and return safely.
Solution
The sign-in flow was updated to allow a controlled Drive return destination while rejecting unsafe redirect values.
Challenge
Authenticated users needed different outcomes according to their assigned role.
Solution
Server-side profile checks now permit only admin and partner roles while other users return to the main site.
Challenge
Application failures required reliable reporting without exposing temporary testing routes permanently.
Solution
Sentry was integrated, tested in production, connected to deployment monitoring, and the temporary validation routes were removed.
Challenge
The current Supabase configuration did not provide the required managed-backup workflow.
Solution
Documented database and Storage backup procedures were created using the Supabase CLI and an isolated Docker-based dump process.
Challenge
The final readiness audit identified navigation and image-optimisation warnings.
Solution
Navigation was moved to the Next.js router, image handling was corrected, and the project reached zero lint errors and warnings.
Current Outcome
The result is a deployed platform that supports professional presentation, authenticated interaction, protected management, operational monitoring, and continued development.
Production deployment at meetshawon.com
Dedicated Drive gateway at drive.meetshawon.com
Authentication, profiles, and account security
Role-based administration and moderation
Full blog and community functionality
Contact protection and custom-domain email
Production exception and uptime monitoring
Documented database and Storage backups
Automated repository security controls
Clean production build and lint results
Public Technical Documentation
The public documentation provides a structured overview of the project objectives, platform capabilities, architecture, technology decisions, identity and access controls, publishing workflows, security engineering, deployment, monitoring, testing, lessons learned, and future roadmap.
Sensitive credentials, private infrastructure details, internal paths, and operational secrets are intentionally excluded from the public edition.
PDF · 20 pages · Public edition
Future Development
The platform is active rather than permanently finished. New content, project evidence, technical writing, and infrastructure integrations will continue to be added.