The big ol’ Build Awesome Internals Pull Request

[zachleat]

The GitHub repository will move from github.com/11ty/eleventy to github.com/11ty/buildawesome (redirects will work)

No breaking changes. No Eleventy functionality has been removed!

Adds support for:

• buildawesome.config.{js,mjs,cjs,ts,mts,cts} Configuration file defaults: https://www.11ty.dev/docs/config/#default-filenames
  • Using a config file with this name will change your log prefix from [11ty] to [buildawesome]
• buildawesome.* Configuration Events match all eleventy.* events: https://www.11ty.dev/docs/events/
• buildawesomeComputed Computed Data: https://www.11ty.dev/docs/data-computed/
• buildawesomeDataSchema for Data Validation: https://www.11ty.dev/docs/data-validate/
• buildawesomeExcludeFromCollections: https://www.11ty.dev/docs/collections/#how-to-exclude-content-from-collections
• buildawesomeImport: https://www.11ty.dev/docs/collections/#declare-your-collections-for-incremental-builds
• Adds .server.js Template file extension (and cjs/mjs/ts/cts/mts) to match .11ty.js (these continue to use the 11ty.js key internally to keep plugin compatibility): https://www.11ty.dev/docs/languages/javascript/
• Adds .data.js Data file extension (and cjs/mjs/ts/cts/mts) to match .11tydata.js: https://www.11ty.dev/docs/data-js/
• Adds buildawesome Global to Data Cascade (alongside eleventy): https://www.11ty.dev/docs/data-eleventy-supplied/#eleventy-variable
• Adds buildawesome:id-ignore attribute support (alongside eleventy:id-ignore) to the Id Attribute plugin: https://www.11ty.dev/docs/plugins/id-attribute/#ignore-a-node
• You can keep using eleventyConfig in your configuration files as-is (you can name it whatever you want) but the docs will likely converge to use a $config convention moving forward.
• The @11ty/eleventy package will continue to be published as normal. This adds a @awesome.me/buildawesome alias.
• process.env.BUILDAWESOME_* environment variables added to match process.env.ELEVENTY_*
• When using the @awesome.me/buildawesome package, the debug prefixes will use BuildAwesome instead of Eleventy. @11ty/eleventy maintains previous behavior. (e.g. DEBUG=BuildAwesome:* npx @awesome.me/buildawesome): https://www.11ty.dev/docs/debugging/

Still pending

• Still need to fence off some of the data location stuff internally
• Empty publish to create the @awesome.me/buildawesome for provenance later
• Rename GitHub repository from 11ty/eleventy to 11ty/buildawesome

[zachleat]

Would have been less big, if the rename were their own PR.

I'm concerned whether the event renames will break existing plugins. But then we should have enough people willing to try a pre-release to catch it, I think.

Just a reminder that the event names are additive and maintain compatibility with existing eleventy event names. You can see that in the AsyncEventEmitter.js code.

[Ryuno-Ki]

Maybe someone else wants to invest a cup of tea to look over it, too.
Generally I'm pleased with the direction it goes (even though there's this nagging feeling that Eleventy is experiencing a corporate capture I can hardly silence here).

[zachleat]

Maybe someone else wants to invest a cup of tea to look over it, too. Generally I'm pleased with the direction it goes (even though there's this nagging feeling that Eleventy is experiencing a corporate capture I can hardly silence here).

Prior to joining Font Awesome I’d been largely carrying a lot of the burden of this project. Might be helpful to go back and re-read this 2024 post https://www.zachleat.com/web/symbiotic-open-source/

I’ve had nothing but support from the Awesome folks for almost two years — they’re great. I’m happy and grateful to be in the Awesomeverse. They’ve shown to me, privately and publicly, many times over that they’re the real deal.

Happy to answer more questions about that, but hopefully this PR shows in code that I’m doing my very best to manage all of these priorities while keeping maximum compatibility for folks that have already entrusted this little project that I started as a brand new parent, checking in that very first late-night commit at 11:27PM in 2017!

[Ryuno-Ki]

Prior to joining Font Awesome I’d been largely carrying a lot of the burden of this project.

I know. I'm glad that you haven't turned your back on it during this whole journey.

Might be helpful to go back and re-read this 2024 post https://www.zachleat.com/web/symbiotic-open-source/

I'm subscribed to your RSS feed 😇
Was a good re-read.

I’ve had nothing but support from the Awesome folks for almost two years — they’re great. I’m happy and grateful to be in the Awesomeverse. They’ve shown to me, privately and publicly, many times over that they’re the real deal.

I trust you. That's why I'm also setting aside time over here to go over big ol' […] PRs :)
But I haven't forgotten the journeys when Eleventy was company-sponsored.
Looking around what management put their money in these days … 😮‍💨
Off-topic. Let's focus on making Eleventy the best it can be.

Happy to answer more questions about that

Yeah. My GoToSocial is acting up (Rate Limiting my server as Podman's networking is masking the forwarded IP. Looking forward to Podman 6 to take another stab at it so I can use the fediverse again).

but hopefully this PR shows in code that I’m doing my very best to manage all of these priorities while keeping maximum compatibility for folks that have already entrusted this little project

It does. I'm riding the alphas on all the projects I regularly commit to.

that I started as a brand new parent, checking in that very first late-night commit at 11:27PM in 2017!

Those were the times *parent here knows exactly what you mean

[zachleat]

Appreciate your review! Definitely made this PR better 🙌🏻

[zachleat]

Shipping with v4.0.0-alpha.8

[cristovaov]

If I may be frank I still think this rename is completely unnecessary, creates more work than it's worth and Build Awesome Pro could have been its own thing running on top of Eleventy.

[zachleat]

@cristovaov sure, it is work. But this is work I’m doing in pursuit of a sustainable project (financially), which the project has never had before — and historically that disparity was just a burden that I carried myself (quietly). Again, I do hope the compatibility story is proof enough that I’m working very hard to minimize the amount of work consumers of the project as a dependency have to do.

[cristovaov]

I absolutely 100% understand Zach. Please don't read me wrong. I guess I care a bit too much :)

edit: and I stay grateful and supportive for the work past, present and future.

[zachleat]

@cristovaov appreciate you! 🙌🏻