Before proceeding, check to make sure there isn’t an existing issue for your suggestion or a similar one.
Idea being proposed
11ty was recently acquired by a company called Font Awesome. It is being rebranded as Build Awesome. They will be providing a hosted, paid “Pro” version of 11ty / Build Awesome, while keeping the underlying static site generator open source. So, according to them, we should be able to carry on as normal except that we’ll want to eventually transition our documentation to say Build Awesome instead of 11ty. And maybe also rename the 11ty-quire npm package too??
In the meantime, they’re running a Kickstarter to fund the effort: https://www.kickstarter.com/projects/fontawesome/build-awesome-pro.
What contribution category does your proposal fall under?
Copyedit text
Supporting Information
No response
Before proceeding, check to make sure there isn’t an existing issue for your suggestion or a similar one.
Idea being proposed
11ty was recently acquired by a company called Font Awesome. It is being rebranded as Build Awesome. They will be providing a hosted, paid “Pro” version of 11ty / Build Awesome, while keeping the underlying static site generator open source. So, according to them, we should be able to carry on as normal except that we’ll want to eventually transition our documentation to say Build Awesome instead of 11ty. And maybe also rename the 11ty-quire npm package too??
In the meantime, they’re running a Kickstarter to fund the effort: https://www.kickstarter.com/projects/fontawesome/build-awesome-pro.
What contribution category does your proposal fall under?
Copyedit text
Supporting Information
No response