Three commits started Noble Strings’ code moving into git, instead of years of untracked changes sitting on the live site. I wrote two shortcodes, [claim] and [dispute], so an article I’m building on the violin maker Knute Reindahl can show a reader which lines are documented and which are only repeated, and moved the site’s custom CSS out of the WordPress database and into the child theme where it belongs.
- Added [claim] and [dispute] shortcodes: an inline pill for a single-sourced or secondary claim, a callout box for the rare case where the primary record contradicts the popular account, in four tiers from reported to unverified. Untagged prose means documented from a primary source; only the exceptions get marked.
- Moved the site’s custom styling out of Appearance > Additional CSS, which stored it only in the database and kept it invisible to review, into a tracked custom.css file in the child theme, loaded after every other stylesheet so it wins.
- Started tracking the site’s own code in git for the first time: the instrument showcase, the news digest, the Google reviews display and the child theme, leaving WordPress core, the database and uploads to Studio.