How This Website Was Built

Purpose and design

This portfolio was created to present my background, skills and projects in one clear experience. Its visual direction is based on the iPortfolio layout: a fixed dark sidebar, a full-screen photographic hero and clearly separated content sections. The implementation and content were adapted around my own profile and work.

The interface is responsive, so the sidebar becomes a mobile menu on smaller screens. The hero contains a lightweight JavaScript typing animation, while the rest of the page remains calm and easy to scan.

Original application: ASP.NET Core

The original version is built with ASP.NET Core 10 and Razor Pages. Razor provides the shared layout, reusable navigation and server-rendered pages. The portfolio does not depend on a database: project and article content is stored in Markdown files and converted to HTML by the application.

The original application includes:

- ASP.NET Core and Razor Pages for routing and page rendering - C# models and a content service for loading Markdown files - HTML and CSS for the layout and responsive design - Vanilla JavaScript for navigation and the typing animation - Docker support for deployment to a server or container platform

Project content

Each project has its own detail page with its problem, approach, result and lessons learned. The Work Order Web App page also explains its security model. Employees receive a unique code, and login becomes available only after an administrator links that code to the correct work account.

Static production version

Because this portfolio does not require a database or private server-side functionality, a second static version is generated from the ASP.NET application. It contains the same pages, design, images, links and animations as regular HTML, CSS and JavaScript files.

The ASP.NET source remains the main editable project and is backed up separately. A reusable PowerShell export script produces the static clone after changes. This approach keeps the original application intact while allowing the public website to run on fast, inexpensive static hosting.

Hosting, domain and HTTPS

The static version is suitable for Cloudflare Pages, Netlify or similar platforms. The custom domain points to the hosting platform through DNS. HTTPS is then issued and renewed automatically by the host, so visitors always use an encrypted connection.

Static hosting also avoids server cold starts. The site can load immediately without maintaining a paid application server, while the full ASP.NET Core version remains available for future development.