what I've picked up over the years about the stupid content tracker
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"$schema": "https://raw.githubusercontent.com/jsonresume/resume-schema/master/schema.json", | |
"meta": { | |
"theme": "even" | |
}, | |
"basics": { | |
"name": "J. Lewis", | |
"label": "Full-Stack Software Engineer", | |
"image": "https://gravatar.com/avatar/e8e17827ad4e795c363687a4ddbd599415a080d00007e5683f44c4dbb89a9be1?size=512", | |
"email": "[email protected]", |
A better solution may be deployment via GitHub Actions, but I stumbled upon a working solution someone else may find helpful. It modifies the shell script found in the documentation a bit to use a workspace to support history
- Vite Static Deployment Documentation 📑
- Inspiration 💡
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/** | |
* Produces an array of locale-respective formats | |
* @template {keyof Intl.DateTimeFormatOptions} K | |
* @template {(NonNullable<Intl.DateTimeFormatOptions[K]>)[]} [F=["long", "short"]] | |
* @param {K} key - a valid key on the `Intl.DateTimeFormatOptions` object | |
* @param {number} quantity - the number of units of the provided option | |
* @param {(index: number) => Date} callback - used for creating subsequent dates | |
* @param {F} formats - an optional list of formats to generate and key | |
* @returns {{ [format in F[number]]: string }[]} | |
*/ |