Tag Redux: `package`, `package-install`, and `package-designer` should we simplify?

Question

So, in reading the question: Package Designer shows blank modal window when clicking "Generate ZIP"

We have three tags in use:

1. package
2. package-install
3. package-designer

Our current strategy has been to label tags after products of Sitecore. For example exm, list-manager, content-editor, experience-editor, to name a few.

If we were to carry this strategy across to package-designer and install-wizard I think that makes a lot of sense.

To me, package is too broad of a tag, and package-install makes me question "if it's on creation" (depending on the question).

So, I'll pose it to the community, what do you think makes the most sense here with these tags?

Answer 1

Something to consider about package tags—we need to take into account that there are (module) packages and update packages. They have different formats, different UIs/tooling and different usage patterns.

Here's a list of all package tags we have right now:

• package
• update-packages
• package-install
• package-designer

There are currently 8 package-install questions and only one package-designer question. Honestly, I don't believe there will be many questions related to creating packages. Most will be related to package installation problems. So I don't think package-install, package-installation or install-wizard make sense—first, they are ambiguous between package types. Second, I doubt anyone will search based on any of these tags.

I can imagine people searching for questions tagged by package-designer, since that's the module that creates packages, and it does have its own tricks and issues.

Proposal

We should concentrate on splitting all package-related questions into packages and update-packages. ^{(Note that we should use the plural form of "packages" instead of "package".)}

We should be left with just two major tags in the end:

• packages (synonym: package)
• update-packages

I propose that we also keep package-designer—it will sometimes be used together with packages. Similarly to how tds will be used for package creation questions of update-packages.

Answer 2

I agree, something needs to be done. package is not a tag I can envision someone would search by or set up an alert for.

I guess package related problems would fall under one of two categories. package-installation and package-creation. I need to look a little bit closer on how people have been using this tag though.

EDIT

Ok I've looked. So. One one hand, I agree, if we follow through on the principle, that the general Sitecore application/product should be in the tag, package-designer and installation-wizard would be appropriate.

I hesitate on the last one however, I don't think most people would notice it is there. They would start typing package and tag auto completion would not indicate it is there. That's why I would prefer package-installation as the second tag. We can then set up installation-wizard as an alias for that tag.

That would be my recommentaion.

TL;DR

We go with package-designer and package-installation. And we create installation-wizard as an alias for package-installation