Research Moving off Jribbble

[ninjulia]

Issue

• Render blocking
• Script not hosted on becausejulia.com (XSS issue)
• Sometimes times out which prompted me to write loading.js to handle loading states (also blocking)
• Written by 3rd party, IDK if it's the latest API vs.

Possible Solutions

• Leverage self-written, self-hosted Dribbble api version 2 with 11ty Fetch native plugin and handling loading errors within the fetch call file
• Last resort: Evaluate using another host for Latest Work section this would be a good reason to redesign that section

Potential Pitfalls

• Currently, the Latest Work section updates every time work is added to my Dribbble account
• This is to keep it low effort / quick win / feature non-case study work
• I'd prefer NOT to use build minutes whenever Dribbble is updated would that require a paid Dribbble account anyway?

[ninjulia]

Resource? Smart Incremental Rebuilds With eleventyImport

[ninjulia]

After completing #54 there have been SIGNIFICANT performance improvements in sitewide JavaScript load times. While I am still embarrassed by the "Just Make It Work" code mess I crafted to leverage Jribbble as it currently stands, I need to de-prioritize this issue in favor of re-addressing those image sizes I thought were nbd 😬.

I also realize moving off of Jribbble is a milestone unto itself, so I will be adding sub-tasks to reflect that.