As an interested user, I watch the Hugo repo, mostly because I like too see how development is going, and have far too many opinions on things. I’ve noticed recently that there are lots of requests for an official shortcode for service X to be part of Hugo.
The issue with allowing ‘some’ shortcodes in is that a line needs to be drawn as to what should and shouldnt be included. The more internal shortcodes there are, the more code there is to maintain. This is especially obvious as GDPR has recently come into affect, and there have been many changes to the internal shortcodes to account for this.
My proposed fix for this relies on the theme composition from https://github.com/gohugoio/hugo/pull/4467. If there was an addition theme, which contained no content pages, but just the shortcodes which originally lived in the hugo binary itself, then users could not only choose if they wanted them, but they could also be edited outside the hugo release cycle. This might be made more interesting with any breaking template changes, if the theme composition doesn’t allow for commit pinning, but that’s separate.
As someone who’s thought through several ways of doing theme composition, and has some really useful generic shortcodes spread around many sites, i’m happy to take up creation / maintenance of this, but I’d like to gauge the community (and Hugo team) opinions on this, and if it’s even remotely a good idea.