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

We have three tags in use:

Our current strategy has been to label tags after products of Sitecore. For example , , , , to name a few.

If we were to carry this strategy across to and I think that makes a lot of sense.

To me, is too broad of a tag, and 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?

  • package has been renamed to packages, package-install has been made a synonym of packages. Oct 30, 2016 at 20:24

2 Answers 2


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:

There are currently 8 questions and only one 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 , or 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 , since that's the module that creates packages, and it does have its own tricks and issues.


We should concentrate on splitting all package-related questions into and . (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:

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

  • As discussed, I second this. Let's give it a go.
    – Mark Cassidy Mod
    Oct 23, 2016 at 10:46

I agree, something needs to be done. 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. and . I need to look a little bit closer on how people have been using this tag though.


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, and 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 as the second tag. We can then set up as an alias for that tag.

That would be my recommentaion.


We go with and . And we create as an alias for

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .