Releases: jsonresume/jsonresume-theme-class
v0.6.0
Visual Changes
This version introduces a few visual changes. I've tried to keep the changes as small as I could get away with—just enough to adhere to the accessibility rules configured in Pa11y. 🙏
Improvements
- Amends several colors to achieve WCAG AAA rule for color contrast ratio. By @SethFalco in #78
- We only add
og:imageif the image provided is an HTTP(S) URL, not for local files. By @SethFalco in #75
Localization
- More Norwegian language support. By @JoeStone13
v0.5.1
v0.5.0
What's New
- Includes Project section to template which was missing before. By @YlanAllouche in #58
- Adds localization support via the
meta.languageproperty. By @SethFalco in #71
Improvements
- Adds more backward compatibility for JSON Resume files written before v1.0.0. By @SethFalco in #66
- Omit month in dates if only a year is specified in the JSON Resume. By @SethFalco in #70
Localization
- Dutch language support. By @JenTheBluePanda
- Polish language support. By @Liental
- Bosnian language support. By @Vukory
- Norwegian language support. By @JoeStone13
v0.4.2
v0.4.1
What's Changed
- Makes a subtle change to colors in light and dark mode. By @SethFalco in #50
- Introduces padding at the top of pages in PDF exports to improve the flow of content over multiple pages. By @SethFalco in #50
v0.4.0
Undoes the language changes introduced in v0.3.0. That was not completely compliant with the spec and is unexpected to users, so I've opted to revert it quickly and replace it with a compliant solution. Consider this a hotfix.
The languages.language property should be a natural language name, but a new property called meta.language has been introduced which sets the document language. It's optional, but strongly recommended for accessibility.
See: https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang#accessibility
What's Changed
- Reverts how
languages.languageis handled to match v0.2.5. - Introduces optional
meta.languageproperty to set document language. - Makes the
<head>of the template a lot more defensive, as every field is optional. This stops including unexpected metadata if certain fields are omitted.
v0.3.0
Various improvements, some changes have a minor impact visually.
A notable difference between v0.2.5 and v0.3.0 is that the languages[].language field is now expected to be a language code rather than a language name. For example, en instead of English. This is used to set the document language for accessibility, and the display name can be determined in runtime through Nodes Intl API.
What's Changed
- Minify the HTML before writing to a file to serve content faster.
- Add the
html[lang]attribute if thelanguagesarray is specified in the JSON Resume. Assumes the first language defined is the language of the document. - Now expects language codes for
languages[].languageinstead of language names. i.e.en, notEnglish. - Links only display the domain rather than the whole URL. i.e. https://example.org/ → example.org
- For the Twitter card logic, also accepts a social media network named "x".
- Clean up CSS and remove the standard reset in favor of our own.
- Remove unused classes from the Handlebars template.
- Updates font-family to include more fonts across operating systems.
v0.2.5
What's Changed
- fix: widen page and make separator color based on theme by @SethFalco in #43
- style: remove padding at bottom by @SethFalco in #44
Full Changelog: v0.2.4...v0.2.5
v0.2.4
v0.2.3
What's Changed
- fix: use human readable date format by @SethFalco in #37
- fix: white background for lightmode by @SethFalco in #38
- fix: move from float to flex layout by @SethFalco in #39
Full Changelog: v0.2.2...v0.2.3