Hey all, an idea I had for people who would potentially want a package forum (a previous built-in feature on Our) instead of using their Github Discussions for this, we could automate a lot of thing.
To opt-in, you would specify the tag name in umbraco-marketplace.json; this will be used to create the desired tag on the forum.
FYI we’ve decided against having public categories in this forum at all (except for Questions and Meta) because people have absolutely no idea what category to post in and we noticed from Discourse that it just ends up with us having to answer “where do I post question about X” over and over again). Hence the suggestion to make tags for them automatically, so people / moderators can tag posts. It is also possible to link to a specific tag so package owners can see the questions just for their tags.
Question is: do you think there’s an actual appetite for package-specific forums? It is nice to have them in 1 place instead of their individual Githubs - makes it a lot easier to find information related to Umbraco interacting with various packages as well.
I like the idea, if I would use it personally is another thing. But for the more polished packages I think it makes total sense.
Got a question about usync tag it, got one about CMSimport or uskinned.
I would suggest we (package group) perhaps try to reach out to the more popular and more polished packages to see if it’s a thing they would want to use.
Since I got a PM on Discord about Cultiv.Hangfire I thought it would be interesting to redirect that one to the forum and have it tagged. I quite like that I can watch a certain tag closely:
I like the idea. My thought is that apart from the core packages there isn’t really a team behind most other packages - but if you’re not committed, just don’t add the tag to your package, right
My idea was that you add cultiv-hangfire as the tag name in your marketplace config file to opt in. You don’t get a tag if you don’t opt in.
My estimate would be a few dozen packages will do this, I don’t see it going nuts at all and I don’t think there’s problems with many tags in the system, should be fine.
Hit the bell notification top right and choose your level of notifications for that tag. So a package developer could be notified of anyone using that tag.
Sounds like there is interest in this, great! Opt-in only makes sense as there’s only really point in doing it if the maintainer is going to subscribe to be notified about the posts with that tag.
So … we plan to support package maintainers opting in by updating the umbraco-marketplace.json file. But for now, if you would like a tag created for your package, please add a comment in this topic and the admins will get it created for you!
Yes opt-in is the way to go imho. But you don’t want a huge list of tags that keeps growing and is never maintained. I’m not sure if you should automate this via the umbraco-marketplace.json.
It’s more work, but I’d rather have a moderator review an application for a tag and have the package creator understand the responsibilities of a tag. And also monitor if the tag is being use AND if the maintainer is active (enough) for it to warrant a tag. It should be removed otherwise. Having a tag for a packages gives an expectation that it means something and gives faster answers.
Or maybe I’m making this too big of a deal, I dunno
Kind of but not really, the interface for selecting a tag then gets super clunky, you’d have to type package and then enter and then type the package name. It’s just not an easy thing to just plop in a tag. From experience, if it’s a 2 step process, people will just skip it entirely.
I think a flat list is also just fine, and I don’t expect a lot of package-specific tags to be added really.
Yeah, I get it! I think people who will opt-in have the desire to actually use it. We can always do periodic cleanups based on tag usage. Am trying not to overthink this one too much either!
I think having the package marketplace file provide the desired tag is a good idea. Then the marketplace website can auto generate a “forum” link using that tag data.
I was wondering if hashtags could be used as “unofficial” tags, like usync and #sql, perhaps searchable…
I’d appreciate this for BlockPreview, had a handful of questions about on Discord that aren’t particularly issues that would live in GitHub. And I agree on the opt-in part
Well, I noticed that if you “#” an actual tag, it will create a tag link… but if you make up a new hashtag, and then later do a search for #sql (for instance), it ignores the “#” and just returns any result for sql - using "#sql" doesn’t make any difference.
So, I guess we can really only use ACTUAL tags for targeted searching.
