In 2024 I was looking for work. I decided to offer my services as a community consultant . Mostly, though, people were interested in technical help getting their Discourse sites fixed or updated. One potential client asked if I could add a contact form for people who didn’t have an account to send fe…

[이미지] jericson: [Failed to load plugin discourse-contact-plugin from http://localhost:4200/assets/js/plugins/discourse-contact-plugin_main-r9hlw1h8.digested.js Error: Could not find module imported from] [이미지] jericson: This was in March and that means I ought to have had until basically…

I went though the same thing with many plugins I had written. I didn’t have the bandwidth to modernize them to the Discourse standard. I have a data science-type job so while I know software engineering concepts, I don’t keep up-to-date with the specifics of web dev stuff. In the end I didn’t update…

[이미지] Moin: I think you got the error because of this bug, not because your plugin needed an update right now Does seem likely. Getting on the latest ESR (and being a bit more vigilant testing) seems like a good plan from now on. [이미지] piffy: I think with the advent of agentic coding, th…

[이미지] jericson: Why hasn’t the plugin tutorial been updated for instance? because we are a fairly small team maintaining a behemoth of a codebase and having to implement new features for paying clients, all the while providing support and keep things working for our open source community. Th…

Thanks for the detailed info @jericson . As you say, Discourse is in a very different position to OpenSSL both in terms of usage & position in the stack. It’s a constant balancing act of progress, customizability, and stability. There’s no perfect solution that will make everyone happy, but we’re alw…

[이미지] chapoi: because we are a fairly small team maintaining a behemoth of a codebase and having to implement new features for paying clients, all the while providing support and keep things working for our open source community. Totally understand. [1] I really like Discourse and I wrote this…

[이미지] jericson: For instance, the tutorial could be turned into wiki posts so that people like me can update them. Why does it need to be a wiki for that? The developer documentation is managed via GitHub. I like the process where the changes are reviewed even more than a wiki. [이미지] Devel…

I agree that the plugin documentation should be updated at this point. The goal of the “depreciation” time period where the plugins still work but the site puts up a warning that they will break soon is to give the plugin authors enough time to fix them. Yet in that time period, a team of full-time …

[이미지] piffy: The goal of the “depreciation” time period where the plugins still work but the site puts up a warning that they will break soon is to give the plugin authors enough time to fix them. Yet in that time period, a team of full-time paid developers couldn’t update the core plugin develo…

[이미지] david: Just to clarify on this point: the deprecation timeline for hbs has only started recently. The earliest we’ll consider dropping support is after the next ESR (end of July). So yes, we should’ve updated the documentation sooner, but this isn’t a case of ‘dropping support without enou…

애호가 플러그인 개발자 사례 연구

개발

Moin 5월 4, 2026, 3:52오후 8

그렇게 하려면 왜 꼭 위키여야 합니까? 개발자 문서는 GitHub을 통해 관리됩니다. 저는 위키보다 변경 사항이 검토되는 프로세스를 더 좋아합니다.

글		댓글	조회수
Deprecating .hbs file extension in themes and plugins Development dev-news	20	1509	8월 9, 2026
A versioned API for client side plugins Development rest-api	33	20275	6월 21, 2024
Preparing for Discourse's upgrade to Ember 5 Announcements	53	8443	4월 8, 2024
Developing Discourse Plugins - Part 1 - Create a basic plugin Developer Guides plugin-guides , tutorial	32	84065	7월 8, 2025
Bundling more popular plugins with Discourse core Announcements	132	10876	3월 19, 2026

애호가 플러그인 개발자 사례 연구

Related topics