Before diving into the substance of the year ahead, allow me a small confession: this post is, in truth, a gentle outline of the posts I plan to share in the coming weeks. I could have tucked these early‑year plans into my New Year letter, but after closing 2025 with a marathon forty‑seven‑minute read, I felt entitled to a lighter start (not to mention my health condition) — and perhaps you, dear reader, deserve one too. Consider this a moment to catch our breath before the next climb, and thank you for your patience and for indulging me in this modest interlude before the more substantial posts begin to unfold.
Of course, the time to tackle the bonus project has come. It is something I announced last summer but never managed to begin. The section‑element series, with its courtroom drama woven into the markup, proved far longer and more intricate than expected — stretching from August 21 to December 25 and transforming what should have been a post or two into a saga within the saga. I hope that this bonus project will remain under control. I envision three posts to carry it through to success. But, as with everything in this saga, simple tasks rarely stay simple once the work begins…
Those four months of wrestling with the <section> element were far from wasted; they became a crucible of learning, shaping both my understanding and my resolve. If you followed the courtroom drama of padding‑left versus margin‑left, you already know these properties stand at the heart of the matter. Yet, as hinted along the way, I must also acknowledge a few missteps in my CSS that now call for correction. That is what comes next. And rest assured — this is not merely about those two properties, nor am I dragging us back into a never‑ending trial.
Two things — or perhaps more. Let me explain. Of course, I have to fix these errors. We are talking about the stylesheet here, and unless you have ever dug into the source code itself, you would not have seen them. Indeed, the posts that reveal my tweaks to the Twenty Seventeen theme, with these mistakes, have yet to be published. My backlog from the earliest days of building this blog is immense: a trove of unpublished chapters that recount how everything came to be, flaws included. That is the CogitActive Saga.
So my plan is twofold: first, to finally bring those long‑delayed posts to light, retracing my initial implementation with its flaws intact; and second, to correct the code in parallel, so that the narrative of the saga and the reality of the blog advance together. Inevitably, this will add new entries to my Blog Post Housekeeping list, but that is part of the rhythm of progress. With four posts already in the pipeline, this sequence should carry us well into mid‑March. And yet, as experience has shown, each “quick fix” often reveals layers far deeper than expected.
As mentioned in my New Year letter, the prospect of searching for a new registrar will have to wait. This is serious business — as I explained in my dedicated post on how to choose a registrar — and it is not a decision to be taken lightly. Thoroughness demands time, and 2026 (much like 2025 before it) will not grant me enough of it, at least not at the outset. Hopefully, I will manage to address this sensitive matter before the year is out. For now, however, I must resign myself to paying the inflated price imposed by gandi.net once again — the cost of caution, or perhaps simply the cost of not having time.
Interestingly, my rudimentary statistics tool has revealed a keen interest in one particular post: Insight Timer free vs. Medito. That entry continues to draw a notable number of visits, which suggests it may be the right moment to share a follow‑up. This time, my focus will be on Medito itself, while also bringing the Healthy Minds Program app into the conversation. In principle, this should be a single post — a straightforward piece of feedback and reflection. Yet I know myself well enough: once I put my finger into the gears, the mechanism tends to spin faster than expected. If it does evolve into another mini‑series, I will save that expansion for the summer instead.
Aside from that, I have — at the time of this writing — nothing else firmly scheduled in my pipeline. Yet, as alluded to earlier, my editorial queue remains packed with those unpublished chapters of the CogitActive Saga, waiting to be polished and released. They alone should keep me busy for quite some time, with the ambitious aim of finally returning to synchrony 1. If I can achieve that — if I can “come back to the future” — then broader advances for the blog and the site may follow: a fresh theme, new features, and, of course, an update on how everything should be done with SiteGround’s Site Tools (since all my earlier demonstrations relied on cPanel). And finally, the path toward the podcast will open once more. And beyond these plans, who knows what surprises may arise along the way…
In the end, these plans are less about checking boxes than about continuing the slow, deliberate work of building something meaningful. Each project, whether small or sprawling, adds another layer to the story of this blog — a story written one post at a time, with care and persistence. The year ahead will no doubt bring its share of detours and discoveries, but that is the nature of the saga: progress made steadily, surprises embraced along the way.
If there are topics you would like me to explore, projects you hope to see unfold, or questions you wish this saga would answer, I warmly invite you to share them. Your requests will spark new directions, and they will help ensure that this blog remains not only my story, but ours.
Thank you, as always, for walking this path with me.
1 By synchrony, I mean the alignment between the blog and real life. Because each topic is explored in depth — and often delayed by the many website‑related tasks that had to precede my first post — the narrative of the CogitActive Saga has unfolded asynchronously. I aim to eventually catch up, so that the posts reflect events as they happen, almost in real time. ^