Daily Dev Habit

Dev Log: Refining the Vision – Beyond Copy/Paste

After setting up the initial foundation and design system for dailydevhabit.com, I paused development. Returning to the project now, the reason for that pause is crystal clear: the core workflow wasn’t complete.

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.

This introduces friction. And friction is the enemy of building a consistent habit.

My goal for this plugin is to create a repeatable, elegant solution for developer documentation. To truly achieve that, the tool needs to close the loop—it needs to handle filing the log, not just producing it.

Where Should Logs Live?

For developer-focused documentation, the most logical destinations seem to be:

  • A GitHub Wiki page
  • A file within a project’s GitHub repository
  • A private Google Doc
  • A new draft post within WordPress itself
  • An email notification

While “Copy to Clipboard” offers flexibility, automating the filing process is key. Sending the log directly to a designated GitHub repository feels like the most natural fit for tracking development progress.

The Roadmap: V0.2.0 – Closing the Loop with GitHub

Therefore, the next major development phase for Daily Dev Habit will focus on integrating a “Save to GitHub” feature. This will involve:

  1. Building a Settings Page: Create a simple admin settings page within the plugin to securely store:
    • GitHub Personal Access Token (PAT)
    • GitHub Username
    • Target GitHub Repository Name
    • Default File Path within the repo (e.g., _logs/)
  2. Updating the UI (JavaScript): Add a “Save to GitHub” button alongside the “Copy to Clipboard” button on the results screen.
  3. Implementing the Backend Logic (PHP): Create a secure AJAX handler or REST endpoint that:
    • Retrieves the user’s saved GitHub settings.
    • Uses wp_remote_post() to make an authenticated call to the GitHub API.
    • Creates a new Markdown file (e.g., YYYY-MM-DD-log.md) in the specified repository with the log content.

This integration will transform the plugin from a helpful utility into a seamless documentation system. This is the immediate priority for development.

More posts