It might save some confusion and help filtering answers.
While we're at it, would a "maker" tag be useful too?
It might save some confusion and help filtering answers.
While we're at it, would a "maker" tag be useful too?
Like so?
I would say 'maker' should get redirect to the Maker category but a tag doesn't hurt.
Or create an Edge category? (I don't have enough privilege for that.)
Just thought about Cloud edition....
(Doesn't much matter to those of use who read everything.)
I think Maker justifies a category because its users are barred from regular support. In general, many topics could apply to multiple editions, where use of tags would be more appropriate.
Edit: Hmmm. Great minds think alike...
I think I can justify a maker category but not any of the other editions, since the maker category is the dedicated support (or lack thereof) hub for maker users; whereas everyone else just files into Ignition and makes it clear what they're using (or doesn't, and we have to guess).
Also, TIL, #maker::tag
makes maker where #maker
makes Maker. What a sentence.