# 62 Discourse fixes and opt-in features from JTech Forums

**URL:** <https://meta.discourse.org/t/62-discourse-fixes-and-opt-in-features-from-jtech-forums/417866>\
**Category:** Development\
**Tags:** development, customization\
**Created:** [19 בנובמבר,‏ 2026,‏ 6:46pm UTC](https://meta.discourse.org/t/62-discourse-fixes-and-opt-in-features-from-jtech-forums/417866 "2026-11-19T18:46:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![TripleU](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tripleu/32/465842_2.png) [@TripleU](https://meta.discourse.org/u/TripleU)\
**Post date:** [20 בנובמבר,‏ 2026,‏ 5:28am UTC](https://meta.discourse.org/t/62-discourse-fixes-and-opt-in-features-from-jtech-forums/417866/3 "2026-11-20T05:28:13Z")

</div>

Thanks for the response. I did read that PRs should have a Meta topic, which is why I made this one. What I missed was that the discussion should happen before opening the PRs. My bad.

Feel free to close all 62 if that’s what makes sense for the team. We already run these changes in our own plugin, so we’re good either way. We figured some of them might help other Discourse sites too.

I’ve always thought of Discourse as this amazing open source project that took off. I hadn’t really thought about what a batch like this costs the team in build time and attention. Your reply put that into perspective for me.

One bit of context: we opened them all at once, but the changes came out of about two years of running our forum and fixing things as we went. I figured the same AI tools that helped us put the PRs together could also help with a first pass at review. I underestimated how much the team would still have to take on.

---

_[View the full topic](https://meta.discourse.org/t/62-discourse-fixes-and-opt-in-features-from-jtech-forums/417866)._
