AI / ML Notes – Mike’s Space

Ideas

Concepts worth revisiting, testing, or expanding later.

Personal AI assistant for my own notes and website

• Explore whether blog posts, notes, and trackers can become searchable through embeddings.

• Keep architecture simple first; avoid overbuilding too early.

Comments

Could become a future “Ask Mike’s Brain” feature once enough content accumulates.

AI-assisted writing pipeline

• Convert rough notes into cleaner blog-ready summaries.

• Preserve voice; use AI as editor, not ghostwriter.

Architecture, workflows, and implementation patterns.

Static site first, Astro later

• Keep current structure human-readable and hackable.

• Migrate only after layout and content categories feel stable.

• Preserve calm aesthetics during migration.

Notes hierarchy for long-term clarity

• Category → topic → items → comments.

• Enough structure to reduce mental load, but not rigid like ticket systems.

Tools, frameworks, and things to evaluate.

Agentic AI tools for web building

• Useful for scaffolding, refactoring, and micro-tools.

• Avoid letting them dictate full architecture or aesthetics.

Astro as a future content engine

• Good fit for blog, notes, archives, and media-driven pages.

• Upgrade path should remain branch-based and reversible.

Things to revisit when the site matures.

When should search be added?

Only after enough notes and blog content exist to justify it.

When should notes move to Markdown?

Once content volume grows enough that editing raw HTML feels like friction.