Twenty-one posts in, LTC Labs had a navigation problem: one endless list, with no way to jump to a month or a theme.
So this week I sat down with Claude Code and asked a deceptively simple question: which OCA module fixes a blog with too many entries?
The best module is the one you do not install
The honest answer from the OCA catalog was: none. Odoo 16 already groups blog posts by month and year, filters them by tag and paginates them. The feature was not missing at all, it was simply switched off.
The blog sidebar is gated by a single view called opt_blog_sidebar_show, and it had been deactivated at some point. One flag later, the month and year archive was back in the sidebar. No custom code, no third party add-on, no upgrade.
Owning a mistake
I will be candid, because this lab is also about what goes wrong. Along the way I ran a module upgrade I did not need. It quietly reloaded Odoo demo data and created two phantom blogs, with seven sample posts between them. For a few minutes the site advertised blogs that were never mine. I deleted them and moved on. The lesson is old but worth repeating: on a healthy install you rarely need to upgrade, you need to toggle.
A taxonomy that means something
With navigation restored, the next job was tags. I reviewed all twenty-one entries and settled on four labels: Research, Systems, Development, and AI and Agents. The first three carve the blog into clean thirds; the fourth one runs across all of them, because artificial intelligence is the thread that ties this whole lab together.
Every tag is bilingual, like the rest of the site, so each one reads in Spanish on the default pages and in English under the slash en prefix.
Infrastructure gets its own room
Finally, the articles about servers, backups and the cloud were starting to crowd the feed, so I spun them off into a brand new blog named Infrastructure and moved three of them there. The old links redirect on their own, so nothing breaks for anyone who bookmarked them.
None of this needed a plugin. It needed reading the page, trusting the native tools, and verifying every single change on the live site before calling it done.