Rebuilding the Site  🔗 **Source:** [Rebuilding the Site](https://lesley.pizza/posts/new-site/) > [!note]+ Document Notes > tags: #astro #static-sites #obsidian #cloudflare-pages #web-development > author: Lesley > source: lesley.pizza > reference: https://lesley.pizza/posts/new-site/ > date created: 2024-12-19 12:00 > > # 🏷️ Title: Rebuilding the site > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Evaluate static site generators for WordPress migration — avoid hosting dependency risks #static-sites - [H2] Set up Obsidian with Git and Templater plugins for content workflow — streamline publishing process #obsidian - [H3] Test Cloudflare Pages deployment pipeline — understand build times and limitations #cloudflare-pages ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [Miniblog Theme for Astro](https://astro.build/themes/) - [Obsidian Git Plugin](https://github.com/denolehov/obsidian-git) - [Cloudflare Pages](https://pages.cloudflare.com/) ## 📝 Summary - Lesley's WordPress site was deleted due to unpaid hosting fees, prompting a complete rebuild - She chose a static site approach using Astro, Obsidian, and Cloudflare Pages for free hosting - The migration involved recovering content from Wayback Machine and setting up a streamlined workflow - Setup difficulty rated 5/10, requiring technical knowledge to guide AI assistance effectively - Final workflow allows publishing with just two keyboard shortcuts in Obsidian ## 📖 Main Content Lesley documents her journey from losing her WordPress site to building a modern static site infrastructure. After her hosting provider deleted her site due to unpaid fees, she saw an opportunity to modernize her approach. The Wayback Machine had preserved most of her content, enabling recovery. Her new stack consists of Astro (static site framework), the Miniblog theme, GitHub for version control, Obsidian as the content editor, and Cloudflare Pages for free hosting. This eliminates ongoing hosting costs while providing a more robust publishing workflow. The setup process revealed important insights about AI-assisted development. While Claude provided technical solutions, Lesley needed domain knowledge to ask the right questions and avoid suboptimal workarounds. Without this expertise, users might accept inferior solutions like manual metadata entry or fragile code implementations. The final workflow is remarkably simple: `cmd+n` creates new posts and `cmd+shift+s` publishes them. The only drawback is waiting for Cloudflare's full site rebuilds on each update, taking several minutes compared to instant CMS publishing. ## 🗒️ Notes **Site Loss and Recovery Decision** - Key idea: Lost WordPress site became opportunity for modernization - Evidence: "I wasn't mad about it. A fresh start wasn't a bad idea." **Technology Stack Selection** - Key idea: Chose static approach to eliminate hosting dependencies - Evidence: "to avoid the possibility of having my entire site nuked because I didn't pay ~$300 worth of annual hosting fees" **Obsidian Integration Success** - Key idea: Obsidian provided unexpectedly flexible workflow customization - Evidence: "I found it super easy to customise every tiny detail of my workflow" **AI Assistance Limitations** - Key idea: AI provides solutions but requires expert guidance for optimal results - Evidence: "Claude would try to solve it once or twice, then, if it still didn't work, Claude would suggest a suboptimal workaround" **Template Configuration Challenges** - Key idea: File structure misalignment caused deployment failures - Evidence: "This meant that the templates couldn't be read by Astro, which caused an error and prevented my site from publishing" **Final Workflow Simplicity** - Key idea: Complex setup resulted in remarkably simple publishing process - Evidence: "cmd+n to create a new post and cmd+shift+s to commit and sync it" **Static Site Trade-offs** - Key idea: Free hosting comes with build time patience requirements - Evidence: "Cloudflare rebuilds the whole site, which can take much longer than just publishing a post on a CMS" ## 📚 References - [Astro Static Site Framework](https://astro.build/) - [Obsidian Knowledge Management](https://obsidian.md/) - [Cloudflare Pages Documentation](https://developers.cloudflare.com/pages/) ## 🗣️ Paraphrase - WordPress site deletion led to modern static site rebuild using Astro, Obsidian, and Cloudflare Pages - AI assistance required technical knowledge to guide toward optimal solutions rather than accepting workarounds - Final setup achieved streamlined publishing workflow with just two keyboard shortcuts, eliminating hosting costs ## 📰 Newsletter **From WordPress Crisis to Static Site Success** When hosting disasters strike, they can become opportunities for modernization. Lesley's experience rebuilding her site with Astro and Obsidian shows how static approaches can eliminate hosting dependencies while streamlining workflows. Key benefits: Free hosting via Cloudflare Pages, simplified publishing with keyboard shortcuts, and recovered content from Wayback Machine. The setup required technical guidance for AI tools but resulted in a robust, cost-free publishing pipeline. This approach could work well for WordPress users seeking hosting independence, though it requires comfort with static site concepts and Git workflows. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Evaluate static export tools for WordPress migration scenarios - Documentation: Create guides comparing static vs dynamic hosting trade-offs - Community: Share case studies of successful WordPress-to-static migrations #### Community - Contributors: Document workflow patterns for Obsidian-based content management - Ecosystem: Research integration opportunities between WordPress and static site generators ## 🧪 Hypotheses - Static sites reduce long-term maintenance burden compared to dynamic CMS hosting - AI-assisted development requires domain expertise to achieve optimal outcomes - Obsidian's flexibility makes it suitable for technical blogging workflows - Free hosting tiers can support small-scale content sites effectively ### 📊 Methodology - Compare total cost of ownership for WordPress vs static hosting over 5 years - Survey developers on AI assistance quality with vs without domain knowledge - Benchmark build times across static hosting providers ### ❓ Questions - How do static site workflows scale for multi-author or enterprise scenarios? - What WordPress features are most difficult to replicate in static generators? - How can AI tools better guide non-technical users toward optimal solutions? ### 🔮 Future Research - Integration patterns between WordPress headless CMS and static generators - User experience studies of technical vs non-technical content workflows - Cost-benefit analysis frameworks for hosting migration decisions ### 💡 Implications - Practice: Static workflows may suit technical bloggers but require setup investment - Policy: Hosting dependency risks affect content preservation strategies - Education: AI assistance effectiveness correlates with user domain knowledge - Funding: Free hosting tiers enable sustainable small-scale publishing ### 🧠 Learning Styles Assessment Reading level estimate: 8th grade #### 👀 Visual learners - Present: Clear workflow descriptions, technology stack overview - Improve: Architecture diagrams showing component relationships, screenshots of Obsidian setup #### 🔊 Aural learners - Present: Personal narrative structure, conversational tone - Improve: Podcast version discussing technical decisions and trade-offs #### 🗣️ Verbal learners - Present: Technical terms explained in context, analogies to familiar concepts - Improve: Glossary of static site terminology, comparison tables #### 🧩 Kinesthetic learners - Present: Step-by-step setup process, specific commands and shortcuts - Improve: Interactive checklist, hands-on migration tutorial #### 🧠 Logical learners - Present: Clear cause-effect relationships, problem-solution structure - Improve: Decision tree for hosting choices, cost comparison spreadsheet #### 🧑‍🤝‍🧑 Social learners - Present: Friend's assistance mentioned, community tool references - Improve: Discussion forum links, collaboration workflow examples #### 🧘‍♀️ Solitary learners - Present: Personal experience focus, individual problem-solving - Improve: Self-assessment questions, independent learning path #### 🌿 Naturalistic learners - Present: Organic workflow evolution, adaptive problem-solving - Improve: Ecosystem thinking about tool interactions, growth patterns ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive text - Improve: More specific alt text for any technical diagrams #### Keyboard navigation - Present: Standard web navigation patterns - Improve: Ensure all interactive elements are keyboard accessible #### Contrast and readability - Present: Clean text presentation, good contrast - Improve: Verify color contrast meets WCAG standards #### Text resizing and reflow - Present: Responsive design principles - Improve: Test at 200% zoom for readability #### Media and captions - Present: Text-based content, no media barriers - Improve: Consider adding video tutorials with captions #### Forms and interactions - Present: Minimal interactive elements - Improve: Ensure any future forms meet accessibility standards #### Standards reference - Content structure aligns with WCAG 2.2 AA guidelines for information presentation ### 🌍 DEIB Assessment #### Cultural breadth - Present: Technology accessible globally, open source tools - Improve: Acknowledge varying internet access and technical infrastructure #### Inclusive language - Present: Gender-neutral technical writing, defined jargon - Improve: Consider alternatives to "nuked" which has violent connotations #### Neurodiversity support - Present: Clear structure, step-by-step explanations - Improve: Add visual breaks, consistent formatting patterns #### Representation - Present: Personal narrative from underrepresented voice in tech - Improve: Acknowledge privilege of technical knowledge and time investment #### Psychological safety - Present: Honest about mistakes and learning process - Improve: Normalize technical challenges, validate different skill levels ### ✅ Logical Validity #### Strong reasoning - Causal reasoning: Clear cause-effect between hosting costs and static migration - Analogical strength: Effective comparison of AI assistance patterns - Inductive strength: Generalizes from specific setup experience #### Fallacies - Survivorship bias: Success story may not represent typical user experience - Anecdotal evidence: Single experience may not generalize to all users #### Tone of voice - Overall tone: Conversational and helpful, acknowledging both successes and challenges ### 🛡️ DARVO Analysis - Deny: No denial patterns present - Attack: No attacking behavior observed - Reverse victim/offender: Not applicable to technical content - Emotional cues and rhetoric: Balanced, self-reflective tone throughout ## 🎯 Conclusion Lesley's site rebuild demonstrates how hosting crises can catalyze workflow improvements. Her Astro/Obsidian/Cloudflare stack eliminated ongoing costs while creating a streamlined publishing experience. However, the setup required technical knowledge to guide AI assistance effectively, highlighting the expertise gap in AI-assisted development. For WordPress users considering static alternatives, this case study shows both the potential benefits (cost savings, simplified workflows) and requirements (technical comfort, setup investment). The approach works best for technically-minded content creators willing to invest setup time for long-term workflow benefits. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] Static sites eliminate hosting dependency risks > [!quote] [Rebuilding the site](https://lesley.pizza/posts/new-site/) by [[Lesley]] via [[lesley.pizza]]. Published 2026-04-16. Accessed 2024-12-19. > "to avoid the possibility of having my entire site nuked because I didn't pay ~$300 worth of annual hosting fees" WordPress site loss motivated migration to static hosting model. [view highlight](https://lesley.pizza/posts/new-site/#H1) #xref #articleseed ID:rw_static_hosting ### [H2] AI assistance requires expert guidance for optimal solutions > [!quote] [Rebuilding the site](https://lesley.pizza/posts/new-site/) > "Claude would try to solve it once or twice, then, if it still didn't work, Claude would suggest a suboptimal workaround" Technical knowledge needed to recognize and avoid AI workarounds. [view highlight](https://lesley.pizza/posts/new-site/#H2) #xref ID:rw_ai_guidance --- ### 🔖 Atomic Split Pad (Zettel Candidates) Purpose: Promote reusable claims into Atomic notes. Split level: H4 #### [Z1] Obsidian enables streamlined technical blogging workflows - When combined with Git plugins and templating - Reference to cmd+n and cmd+shift+s shortcuts - Links: [[Content-Management]] [[Static-Sites]] #### [Z2] Static site build times create publishing friction - Cloudflare Pages rebuilds entire site on each update - Trade-off between cost savings and immediate feedback - Links: [[Publishing-Workflows]] [[Performance-Trade-offs]] --- ### ✏️ Fleeting Queue Purpose: Capture quick actions for Fleeting notes. - [F1] Research Obsidian Git plugin setup — evaluate for content workflows #fleeting #inbox - [F2] Compare static hosting rebuild times — benchmark performance across providers #fleeting #inbox - [F3] Document AI assistance patterns — identify expert guidance requirements #fleeting #inbox <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Rebuilding the Site.md|Rebuilding the Site by lesley.pizza]] ## Highlights - This felt really finicky. Fortunately, I knew to ask it if there was a way that I could turn this into a template. It then suggested I download a plugin on Templater. ([View Highlight](https://read.readwise.io/read/01kpb9f749v9w61d6b197y9xsf)) - Tags: 👻 ai highlighted