Skip to content

📝 Documentation: Refer to Bingo as a "framework", not an "engine" #2199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
JoshuaKGoldberg opened this issue Apr 9, 2025 · 1 comment · Fixed by #2200
Closed
2 tasks done

📝 Documentation: Refer to Bingo as a "framework", not an "engine" #2199

JoshuaKGoldberg opened this issue Apr 9, 2025 · 1 comment · Fixed by #2200
Assignees
Labels
area: documentation Improvements or additions to docs status: accepting prs Please, send a pull request to resolve this!

Comments

@JoshuaKGoldberg
Copy link
Owner

Documentation Report Checklist

Overview

I'm writing announcement docs for Bingo in bingo-js/bingo#246. Part of publicly promoting a thing is figuring out its nomenclature. One nomenclature normalization I'm going to go with for Bingo is:

  • "Engine": will refer to the tooling on top of Bingo, i.e. for now Handlebars and Stratum
  • "Framework": Bingo itself, akin to Express or React

Additional Info

Marking this as a docs issue even though it'll be a fix: in PR to update generated README.mds.

🎁

@JoshuaKGoldberg JoshuaKGoldberg added area: documentation Improvements or additions to docs status: accepting prs Please, send a pull request to resolve this! labels Apr 9, 2025
@JoshuaKGoldberg JoshuaKGoldberg self-assigned this Apr 9, 2025
JoshuaKGoldberg added a commit that referenced this issue Apr 9, 2025
Copy link

github-actions bot commented Apr 9, 2025

🎉 This is included in version v2.40.3 🎉

The release is available on:

Cheers! 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation Improvements or additions to docs status: accepting prs Please, send a pull request to resolve this!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant