www.christian-schwanse.com - Portfolio Website

On the website I present myself, my skills, professional experience and projects.
The portfolio website itself is also a project.

General Information about the Project

• Client: Myself
• Project Goal: Demonstrate my skills, professional experience, projects and learn frontend web development without a framework.
• Number of Project Participants: 1
• Period: May, 2024 - July, 2024 (+ new implementations from time to time)
• Sector / Area: General / Web Development
• Role: Lead Developer
• Languages: German, English
• Result: A website that can be found on the Internet by all kinds of interested parties all over the world. Also a significant improvement in front-end web development skills (HTML, CSS and JavaScript).

Tech Stack:

• HTML
• CSS
• JavaScript
• Inkscape
• Github
• MS Visual Studio

How I worked on this project

Planning at the beginning. Answering questions such as:

• How do I want to implement the website?
• What scope should the project have - taking into account that I work and have other commitments?
• Which pages and content should the website contain?
• Who should the website be aimed at and how should it be accessible / findable (e.g. marketing)?

Once the planning was complete, it was time to get down to business - a cycle consisting of the following steps:

• Planning a work step for a new functionality
• Programming
• Testing
• If successful: Code Refactoring. If failed: Bug Fixing
• Testing
• Github Commit / Push

Why I implemented the project in this way

I developed this website without a framework - just the lovely triangle: HTML, CSS and JavaScript.
Reason: It's my first real, self-programmed website. I'm generally a fan of practicing the basics first before venturing into new, "interesting" things.
I also had the thought that I would clearly see the advantages and compromises of frameworks in the future.

My 3 most important points that I have learned from this project

1. Create your own components such as headers or footers that can be can be reused across pages.
2. Structuring of a web development project (e.g. file management or components)
3. It is very time-consuming to develop a website (including content) from scratch. Figma would make sense in the long term. A tool for designers and developers to create prototypes of UIs. This avoids the case of programming something for a long time and then discarding it in the end because you don't like it after all - I'd rather not say whether this happened to me during the project 😉 Todo management software such as Jira is also helpful.

I look forward to you visiting my website and having a look around!


Greetings

Chris