Details : A CV/Portfolio Single Page Website template for individual use with custom CLI-based CMS, helping you to change information in your CV website as you require. Beware! There will be a Glitch in your CV! :)
License Info : 
This is the version 0.1.0. Stable version coming soon!
GlitchCV is a personal single page static CV/Portfolio website template. It is minimalistic, user-friendly, fully responsive, and most-importantly, "dynamically static".
For most static website templates out there, you need to look up a bit of HTML and CSS to set them up. I, however, wanted to make a web template where I can just plug in data somewhere separately, and it will be set. Therefore, I designed a Command Line based CMS Interface for GlitchCV to use to load the data dynamically (without any server-side code!) via front-end rendering. You can say it's like a flat-file CMS (for example - Grav), but it's not as interactive and advanced (and definitely does not have a GUI!) as it sounds. However, the headache of figuring out how to fit the new content you want to insert is significantly reduced.
GlitchCV is completely open-source and free to use. Also, the website changes its color daily!
This template is easy to figure out (or so I tried to make). All you need to do is fill in the necessary data in the JavaScript files located in ./resources/ in the project directory. Go to User Manual to learn how to configure the website.
To start, you need to know how to work with JS Object format. You can start by reading the official MDN docs and this W3Schools JS Object Intro.
data.jsfile contains all of your necessary information to configure the website. This KEY file should be updated whenever you want to make any changes in content.settings.jsfile contains few dynamic settings information. In most cases, you may not need to configure this file at all. Ideally, unless you know how Arrays, CDNs, Fallback Methods work, you should not touch this file with confidence.
Proceed to User Manual to learn more.
I have these improvements in mind -
- Changing the cms files into
JSON: I wanted to use JSON files instead of JS for loading data and settings since the start. I tried and I failed repeatedly. As my self-committed deadline approached soon, I had to put it aside and use.jsfiles to load data. So, there is one improvement I have in mind. Or is using JS files better here? Well, I guess JS files are taking less space and if you, the user, want to minify them to use, it will take even less space. - I want to integrate a clients section. This section will have a Moving display.
- I am having ecod thoughts about using percetages to explain your skills. To me, that's simply pretentious. However, many are so I guess I will add it as a feature.
If you think you can make any improvements here (incl. the above sighs), fork the project, add your improvements and open a pull request. I will check it and discuss with you.