Author: lbdev
-
Dev Log: From Plugin to Platform – The Two-Stream Architecture
In my last post, I signed off with a simple plan: test the “Save to GitHub” feature and deploy. But as I started using the tool, I realized that saving Markdown files to a repo was only half the solution. If I truly want to build an “Engineering Intelligence” tool, I need more than just…
-
Dev Log: Laying the Foundation for GitHub Integration
Following up on the previous post where I defined the vision for v0.2.0, integrating a “Save to GitHub” feature, today was all about building the necessary foundation, both in the plugin’s code and in my own development environment.
-
Dev Log: Refining the Vision – Beyond Copy/Paste
The current version of the Daily Dev Habit plugin (v0.1.0, available on the live demo) successfully guides users through journaling prompts and generates a clean Markdown log. However, the final step relies on “Copy to Clipboard,” forcing the user to manually switch contexts and paste the log into its final destination.
-
Dev Log: The Origin of a Habit
Before I left for WordCamp US in Portland, Oregon, my days were a blur of context-switching. I was juggling my day job, architecting OcalaRepair, and rebooting One Off Boss. Hopping between these complex projects was taxing; I’d return to one after a few days away, and the details would escape me.
-
Daily Dev Habit Design System
The first post for Daily Dev Habit is the Design System. This can be used as a template for designing other sites. The Full Site Editor is used on this site, no custom templates or theme builders.