Personal portfolio 👨‍💻

This is my most recent portfolio website in which I share my projects.

Click here for the live demo

Table of Contents 🧭

1. Goal
2. Getting started
3. Wishlist
4. Practises

Goal 💪🏻

The goal of my personal website is to exhibit the projects I have been working on lately.

Getting started ✨

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Technical requirements

To run this project you'll just need a browser.

📥 Installing

1. Clone this repository 👯

Before we can get started, we'll need to clone this repository or download the files. We can do this by typing the following line of code in the terminal:

git clone https://github.com/InjuMichorius/personal-portfolio.git

Or downloading the files

2. Open html with browser 💻

Go to the folder and open (for ex.) index.html in your browser

Feature wishlist / backlog 👑

Below is a list of features I'd love to add to this application. The features are split up using the MoSCoW method.

M - Must haves These features are requirements for the end product

• Reponsive website
• Hero section
• Project section
• Reach out
• Project detail

S - Should haves These features are wanted, but not necessary for a usable product

• Navigation
• Accessible standards
• Mobile friendly

C - Could haves These features can be added if there is enough time to do so

• Play video on hover
• Add calendar management like cal.com

W - Would haves These features can be added in the future

• Content for all projects

Design patterns and Best Practices 👩🏻‍💻

Code standards are important when working on any project; your code stays consistent and is readable for everyone. I defined code standards for HTML, CSS and JS while working on this project.

Javascript code standards

• Variables & functions are written in camelCase
• Promises are handled with async functions using await
• I don't use var, only const or let
• I put spaces around operators ( = + - * / ) and after commas (exception for for loops)
• I use indentation with TAB
• I always end a statement with a semi-colon;
• Functions have their opening bracket on the same line as the name, with 1 space in between
• I use ES6 syntax where possible

CSS code standards

• I try to avoid !important as much as possible
• Layout/general styling is always above more specific styling
• Selectors are not unnecessary long nor short
• I use CSS3 syntax where possible
• I avoid old display properties like float
• CSS Selectors must have a space between the name and bracket

HTML code standards

• I only use IDs when the element is present once on a page and it's necessary for styling or Javascript
• I always write semantic HTML according to W3C Validator
• Divs are only used when necessary for styling purposes
• Classes allow easy re-usage
• Indentation is always clear

License 🔐

This project is licensed under the MIT license by © Inju Michorius, 2024. See the LISENCE.md file for details.