11ty Config Cleanup

[xjensen]

This PR cleans up our management of content metadata. Nowadays 11ty offers many options, such as the full Data Cascade, to help process content. Let's use 'em.

[github-actions]

Preview site available at config-cleanup-1.pr.digital.ca.gov.

[zakiya]

Once this is done I'd like to apply it to hub.innovation.ca.gov and abortion.ca.gov.

[jbum]

OK, this first set of fixes doesn't apply to hub, nor abortion, because they aren't wordpress based. I do love the idea of using 11tydata.js files for page-specific 11ty code.

[zakiya]

For some reason I keep forgetting that innovation has a WordPress backend. Denial?

[xjensen]

I've got two more big changes ready for consideration.

First, the PAR scores have been integrated into 11ty's Data Cascade. We no longer need the npm run readability script, the collection of Nunjucks filters used to format PAR data, etc. This code has been relocated to pages/_data/eleventyComputed.js.

Second, I've brought in 11ty's navigation plugin, which we can use to create the breadcrumbs a bit more easily.

[jbum]

Very nice, I'll review this afternoon.

…

On Tue, Jan 9, 2024 at 11:03 AM Jon Jensen ***@***.***> wrote: I've got two more big changes ready for consideration. First, the PAR scores have been integrated into 11ty's Data Cascade. We no longer need the npm run readability script, the collection of Nunjucks filters used to format PAR data, etc. This code has been relocated to pages/_data/eleventyComputed.js. Second, I've brought in 11ty's navigation plugin <https://www.11ty.dev/docs/plugins/navigation/>, which we can use to create the breadcrumbs a bit more easily. — Reply to this email directly, view it on GitHub <#242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACGJ2N3LEBYSMA3S5KVC7TYNWIBBAVCNFSM6AAAAABBNGYGQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBTGYYTSNZVGQ> . You are receiving this because you commented.Message ID: <cagov/innovation .***@***.***>

[jbum]

@xjensen I am currently getting a local build error on this branch (after running npm install; npm run dev) -- does not occur on main branch.

[11ty] Problem writing Eleventy templates: (more in DEBUG output)
[11ty] 1. Having trouble writing to "_site/blog/posts/helping-californians-have-a-voice-in-toxic-cleanup-projects" from "./pages/blog/posts/wordpress-posts/helping-californians-have-a-voice-in-toxic-cleanup-projects.html" (via EleventyTemplateError)
[11ty] 2. EISDIR: illegal operation on a directory, open '_site/blog/posts/helping-californians-have-a-voice-in-toxic-cleanup-projects' (via Error)
[11ty] 
[11ty] Original error stack trace: Error: EISDIR: illegal operation on a directory, open '_site/blog/posts/helping-californians-have-a-voice-in-toxic-cleanup-projects'

Also curious about the changes to the readability method. Previously if I wanted to test a readability run, I would run npm run readability followed by a build. It looks like you have the readabiity pass built into the build now, is that correct? So theoretically, if I just do npm run dev I get fresh values? (cool if so)

[xjensen]

I got that error too, but never figured out why. It went away when I did a manual delete of the _site build folder. I should probably investigate.

Yes, the readability scores run fresh on every build. We could probably re-do the readability.json file as an on-demand script if that would be useful for debugging.

[jbum]

Yeah, that fixes it. Approving... Merging...

[jbum]

Reimplemented readabiity scores in a more efficient way.

[jbum]

Nvm, looks like this is still in draft mode...

[xjensen]

I'll have it ready soon.

Not planning to make any more big changes. Just want to make sure the site still behaves as expected.

[xjensen]

@jbum I think this is ready for review.

[jbum]

Looks good -- go ahead and merge :)