content: replace blog.json with single post (2026-03-24)

CHANGELOG-rollback-2026-03-24T22:06:43Z.md

@@ -0,0 +1,26 @@
+Rollback and Recovery Changelog
+
+Timestamp: ${TS}
+
+Actions performed:
+- Reset main branch (working tree and HEAD) to commit 6127867d51c9f0e4e86d1d8390081208f45136ab and force-pushed to origin/main.
+- Confirmed README.md content matches version at commit 6127867d51.
+- Investigated deleted backups: located backups in parent commit 5189b23 and extracted available files into recovered_backups/ directory in the working tree (not yet committed).
+- Created this changelog and saved recovered backup files under recovered_backups/ for review.
+
+Recovered backup files:
+- backups/index.html.20260324164129.bak -> recovered_backups/index.html.20260324164129.bak (extracted from commit 5189b23)
+- backups/index.html.bak.20260324164053 -> recovered_backups/index.html.bak.20260324164053 (extracted from commit 5189b23)
+
+Notes on recovery:
+- The deleted backup files were present in previous commits and have been extracted from git history into recovered_backups/.
+- Additional backup files referencing other timestamps exist in git history (e.g., backups/index.html.20260324164556.bak and backups/index.html.20260324164626.bak). These can be extracted on request.
+
+Suspicious findings:
+- Commit 6127867d51 (message: "Deleted Backups and changed readme") removed backup files. Author: Oliver. This commit may be responsible for missing backups. Please confirm whether this deletion was authorized.
+
+Remaining tasks / recommendations:
+- Decide whether to reintroduce recovered backups into main branch. Restoring them to main will create a new commit on top of 6127867d51 (this changelog can be used), or they can be provided in a separate branch or as artifacts.
+- If you want me to commit the recovered_backups/ content and this changelog to the repository and push, confirm and I will proceed.
+- If you prefer the repository to remain exactly at 6127867d51 (no additional commits), I will not commit recovered files; instead I will provide them separately (download/attach) and leave main at the rollback state.
+

blog.json

@@ -1,15 +1,22 @@
-{
-  "posts": [
-    {
-      "id": "how-odoo-makes-donor-management-easy",
-      "title": "How Odoo makes donor management easy",
-      "date": "2026-03-24",
-      "author": "Odoo4Projects - NGO team",
-      "categories": ["donor-management", "transparency", "productivity"],
-      "tags": ["Odoo", "donor communication", "automation", "minimal admin"],
-      "excerpt": "Learn how Odoo reduces administrative effort, improves donor communication, and increases transparency for NGOs.",
-      "content": "Odoo makes donor management easy by centralizing donor data, automating receipts and updates, and generating transparent reports donors trust. With minimal admin required, NGOs can set up templates, schedule automated communications, and track gifts and commitments in one place. Donors receive timely receipts and impact updates that strengthen trust and retention. Odoo’s dashboards provide simple, exportable reports for accountability. The result: less time on admin, more time on mission.",
-      "featured": true
-    }
-  ]
-}
+[
+  {
+    "area": "Donor Management",
+    "title": "From Notebooks to Night Off: How One NGO Cut Reconciliation Time in Half",
+    "teaser": "<p>Ana replaced stacks of notebooks with a single shared ledger and reclaimed her evenings.</p>",
+    "content": "\"Ana used to sit under a single lamp with three notebooks stacked and the weight of every donor question on her shoulders. When a donor called she fumbled through pages and felt her chest tighten.\"\n\nAn ERP creates a single source of truth for every donation: each peso is recorded once and linked to allocations, program expenses, receipts, and impact notes, eliminating duplicated spreadsheets and manual cross-checks. Shared dashboards, ownership fields, and due-date tracking make reconciliation predictable and reduce the time teams spend hunting for evidence.\n\nWith Odoo and n8n, donors submit a simple webform that triggers an n8n workflow to create the donation card in Odoo, attach receipts, apply tags, and notify the approver. Approval buttons in Odoo, automated reminder sequences, and scheduled exports or AI summaries transform reconciliation into a short weekly routine and let audit packets assemble automatically.\n\n\"Now Ana closes her laptop at 7 p.m., answers donor queries in seconds from a shared dashboard, and walks home without the knot in her chest — the night no longer belongs to reconciliation but to rest.\"\n\nGet a free trial: https://ngo.odoo4projects.com",
+    "date": "2026-03-24",
+    "slug": "from-notebooks-to-night-off",
+    "author": "Odoo4Projects NGO",
+    "categories": [
+      "Donor Management",
+      "Efficiency"
+    ],
+    "tags": [
+      "Odoo",
+      "n8n",
+      "reconciliation",
+      "donor-management"
+    ],
+    "meta_description": "How one NGO replaced stacked notebooks with a shared ledger and cut reconciliation time in half using Odoo + n8n."
+  }
+]

index.html

@@ -1,3 +1,6 @@
+</html>
+
+
 <!DOCTYPE html>
 <html lang="en" class="scroll-smooth">
 <head>