Use Case Scenario:
Developer uses shortcodes and snippets in all client sites. Developer uses the same shortcodes for template type content.
Example:
Template type pages are just copied over to new sites. Like pages with site legal text: terms of use, privacy policy, cookie policy, etc... Developer uses shortcodes to automatically pull important site info into legal text.
- Site Title
- Site URL
- Site Admin Email
- anything really...
Issues with current shortcodes:
- The “Woody” shortcodes would be different on each site. The developer would have to make sure that each shortcode matches all of the shortcodes on each template page.
- The shortcodes would change everytime they are imported, created or re-created on a site.
- Woody shortcode names don’t provide any useful info to developers or front end users. If there is an error with the plugin, the php, or if the plugin is accidentally disabled... then the users on the front-end see a shortcode that doesn’t make any sense. A more functional driven development are shortcode names which provide some clear information as to what the shortcode is trying so display. For example, instead of shortcode named like this: [wbcr_snippet id="37"], it could be named like this [site-name]. Providing a name for the shortcode gives clear insight that the shortcode is probably there to provide the website’s name. So even if there the shortcode isn’t working, it still provides info to the user. It also provides the developer clear info.