... | ... | @@ -2,10 +2,12 @@ |
|
|
|
|
|
# Known labels
|
|
|
|
|
|
* [events](https://lab.civicrm.org/explore/projects?tag=events)
|
|
|
* [cart](https://lab.civicrm.org/explore/projects?tag=cart)
|
|
|
* [cases](https://lab.civicrm.org/explore/projects?tag=cases)
|
|
|
* [events](https://lab.civicrm.org/explore/projects?tag=events)
|
|
|
* [locations](https://lab.civicrm.org/explore/projects?tag=locations)
|
|
|
* [scheduledreminders](https://lab.civicrm.org/explore/projects?tag=scheduledreminders)
|
|
|
* [tokens](https://lab.civicrm.org/explore/projects?tag=tokens)
|
|
|
|
|
|
# Label structure suggestions
|
|
|
|
... | ... | @@ -13,5 +15,5 @@ These are somewhat arbitrary suggestions by @bgm. Feel free to discuss in the [e |
|
|
|
|
|
* If it is related a components (events, memberships, cases, etc), use the plural form when it is something that is usually pluralized (many events, but only one cart).
|
|
|
* Always lowercase
|
|
|
* Spaces are OK if it really makes sense? (see next point)
|
|
|
* Avoid spaces (ex: scheduledreminders)
|
|
|
* Avoid tags very specific to one extension. Obviously this is very subjective, but say there is only one extension for "Jupiter Address Formatting", and it's the only extension for Jupiter, then the Jupiter tag might not be relevant. 'geolocation' would be a good tag. 'address'? hard to say, since people are unlikely to search by "address extensions", but more likely to search for "address formatting". |
|
|
\ No newline at end of file |