-
v5.2.0
v5.2.0: Add dynamic footer badges This release marks the introduction of a new feature, dynamic footer badges. This marks another step towards a template-driven theme that could be reused for other general purposes. Previously, the site hard-coded the three different site footer badges into the theme `footer.html` partial file. Now, the partial checks for content in a `footer` section/category, and renders the badges from the site content first. Each badge exists as its own AsciiDoc/Markdown file. Going forward, the intention is to continue making the theme generic so it can be released independently as a new theme.
-
v5.1.0
v5.1.0: Update Bootstrap from v4 to v5 This release updates the underlying web framework behind my site, Bootstrap. Last year, Bootstrap releases v5, which included dropping the jQuery dependency. The site also better utilizes several Bootstrap classes and elements, which makes it scale better on mobile devices. See more details about the v5 change: https://blog.getbootstrap.com/2020/06/16/bootstrap-5-alpha/
-
v5.0.1
v5.0.1: Required tweaking to take Hugo to production This tag represents the point where I took the Hugo-generated site to production and retired my Jekyll-powered site. Notable changes since the initial launch: * **CI**: Use a Rubygem, htmlbeautifier, to tidy HTML and convert all spaces to tabs before publishing the HTML in the `deploy` job. * **Theme**: Show metadata in `<head>` that only appeared in certain circumstances, remove extraneous HTML that broke HTML validation. * **Robots.txt**: Tell search engines to ignore the `/what/` directory since it only contains HTML that is embedded on the index page. Similar to how `/content/` was used on the Jekyll site.
-
v5.0.0
v5.0.0: Hello Hugo! This tag marks the initial migration of my personal website to Hugo. It is a near-total page-for-page match of what existed in the Jekyll site. The changes are deliberately meant to match the existing content. Anyone visiting the site would not be able to tell the difference in the static site generator without inspecting the HTML. I made this change for a few reasons: * github.com/unicef/inventory, a work project, uses Hugo. Using Hugo for my own site gives me more opportunities to better learn the tool. * Hugo templates offer more creative opportunities for how I utilize my website. I am also maintaining a general-purpose theme that I could utilize for building other websites. * Keep my web development skills sharp by using another templating engine to manage my personal site.
-
v4.3.0
v4.3.0: Final Jekyll-built version of site This tag marks the final state of the Jekyll-powered site before it was retired and moved to Hugo. This includes all improvements, changes, and other tweaks made to the Jekyll site since the last release. See the git commit history for a detailed overview of changes.
-
v4.2.2
v4.2.2: Migrate to AsciiDoc This tag marks the shift from Markdown to AsciiDoc. I integrated the `jekyll-asciidoc` plugin to my Jekyll config, which was made possible by moving to GitLab and using any version of Jekyll and plugins that I wanted.
-
v4.2.1
v4.2.1: Relicense from MPL-2.0 to GPL-3.0 I probably had a reason for this at the time, but I forgot now.
-
v4.2.0
v4.2.0: Migration from GitHub to GitLab v4.2.0 is a periodic release to demonstrate the transition of the website from GitHub to GitLab. After this time, the CI pipeline was able to move beyond TravisCI and GitHub Pages. Versions of the site after v4.2.0 use a newer version of Jekyll and also modifies how continuous integration is handled going forward.
-
v4.1.0
v4.1.0: New fonts, new features, and complete back-end rewrite v4.1.0 is a feature release for my website. Most noteworthy is the migration of my content from raw HTML (which Jekyll served) to more modular content, stored in Markdown, and then compiled and served By Jekyll. This makes my website significantly easier to maintain. Some other details worth noting: * New fonts used across home page * Old, archived sites now live in `archive/` * Archived sites have various broken links fixed * Move domain from `justinwflory.com` to `jwf.io` * Add `jekyll-sitemap` to build sitemaps along with the site * Fix misc. errors reported by Google and Bing webmaster tools
-
v4.0.0
v4.0.0: Initial launch of Jekyll-based personal website Woohoo! This is finally done. I have wanted to do this forever. My site is now a Jekyll-based static site. For now, it is a direct port of HTML and CSS from the v3.1.1 site, but the modularity and flexibility leveraged here by Jekyll is more aligned to what I always wanted my website to be like. v4.0.0 is a stepping stone to getting my site to something I am a little more proud of. All that high school tech debt is slowly getting paid off. 15 year old me would be proud.
-
v3.1.0
v3.1.0: Modularize nav, header, footer and update content Originally tagged 2018-03-25. Tag updated to use semantic versioning on 2020-03-14. No other changes.
-
v3.0.0
v3.0.0: First release of v3.0 of my website Originally tagged on 2018-03-25. Tag updated on 2020-03-14. Also the tag originally pointed at commit 5c2df834823b7c7576db3c34ca0cb2a62e2332c5, but commit bfa42d62d4fcb61270d60fb66a66be00b8333da8 actually describes the first commit of v3.0.0, which was an earlier commit. :shrug: Changelog ========= This gets a start and at least makes it look a little different. More additions will be made soon. Some things that changed: * Original, original version of the website moved to /v1/ * Previous version of the site moved to /v2/ * Fixed AP Exam Books URL * Permanently deleted the /music/ app * Other housework
-
v2.0.0
v2.0.0: Initial port of HTML to git This is the initial commit of v2.0.0 of my personal website. When this commit was pushed, I was maintaining the raw HTML source of my website on a server. So there was no version control tracking! Of course, when I first started developing my website, I was maybe 14 or 15, and just starting to figure out the whole Linux server and git stuff. But a little bit of historical context never hurt. :smile:
-
v3.1.1
v3.1.1: Where my website currently stands This is a release mostly motivated by the fact that I am starting to explore how to migrate my personal website to a Jekyll-based deployment. Jekyll will make it easier for me to manage this website over time instead of the ugly HTML that I am doing right now. So, this is a historical snapshot to remember for "some day".