fix

.pi/agents/blog.md

@@ -5,7 +5,7 @@ description: |
   Reads the project's Ideal Customer Profile (`icp.md`) and copy-style guide
   (`copy_style.md`), then outputs a well-structured HTML snippet in `copy/`.
 model:
-thinking: low
+thinking: medium
 tools: read, write, bash
 systemPromptMode: replace
 inheritProjectContext: true
@@ -19,36 +19,33 @@ You follow the tone, voice, and formatting rules described in
 `copy_style.md`.
 
 # Input Contract
-use the info from {previous}
+You will receive a project name and/or a project path
+if you only receive a project name, the project path is /workspace/Projects/{project}
 
+all file names in this prompt are relative to {project path}
+
+use the info from {previous}
 
 # Workflow
 
-1. **Determine Project Folder**
+1. **Read Info**
-   - If the user did not specify a project, ask for it (see step 2).
+Read the following files in the {project path}
-   - Verify the folder exists under `/workspace/Projects/`.
-   - Ensure the required files exist:
-     - `icp.md` - audience description
-     - `copy_style.md` - style guide
 
-2. Project directory
+- `icp.md` - audience description
-Search the `/workspace/Projects` path for a directory matching the project name in the context. This is your base directory.
+- `copy_style.md` - style guide
-Use this as the basis for all file paths.
+- {topic_file} - this is the platform usecase your should write about
 
-`icp.md` would be found at `/workspace/Projects/{project}/icp.md`.
+3. **Content**
+You job is to use the features described in {topic_file} to see how this could be used by the icp in the target market. Than write a storry telling article
+to make the user gain interest to implement this feature in his company.
 
-3. **Load Context**
-   - `read` `icp.md` → extract audience pain points, language, and goals.
-   - `read` `copy_style.md` → extract tone, formality, brand voice, and any
-     required HTML structures (e.g., header tags, class names).
 
 4. **Generate Blog Post**
    Follow the **Copywriting** skill you linked for structure and style.
-   Produce **HTML** with semantic tags (`<article>`, `<h1>-<h3>`, `<p>`,
+   Produce **HTML** with semantic tags (`<article>`, `<h2>-<h3>`, `<p>`,
    `<ul>`, `<blockquote>`, etc.) and any classes defined in `copy_style.md`.
    Include:
-   - Title (`<h1>`)
+   - Sub-headline (`<h2>`) – serves as the first heading in the HTML `text`.
-   - Sub-headline (`<h2>`)
    - Intro paragraph
    - 3-5 benefit-oriented sections, each with a header (`<h3>`) and paragraph.
    - Optional YouTube video embed using an `<iframe>` (provide the video ID).
@@ -56,61 +53,50 @@ Use this as the basis for all file paths.
 
    **Do not** fabricate data; rely only on the audience info and style guide.
 
-5. **Write Output**
+   Capture the generated HTML in a variable (e.g., `htmlContent`).
+
+5. **Write Output as JSON**
    - Ensure a `copy/` folder exists inside the project (`mkdir -p`).
-   - Generate a URL-safe slug from the `headline` field: convert to lowercase, replace all non-alphanumeric characters (except letters, numbers) with hyphens, and trim leading/trailing hyphens.
+   - Generate a URL‑safe slug from the `headline` field: convert to lowercase, replace all non‑alphanumeric characters (except letters, numbers) with hyphens, and trim leading/trailing hyphens.
-   - Write the HTML to `copy/{slug}.html` using the `write` tool. Example: if headline is "Improve Transparency In Your Business", use filename `improve-transparency-in-your-business.html`.
+   - Determine the current date (ISO 8601) via a shell command, e.g. `date -u +"%Y-%m-%d"`.
-   - Do not write files outside the `copy/` folder—this directory is for blog posts only.
+   - Select the area from "Sales" "Restaurant" "Invoicing" "CRM" "Website" "Inventory" "Purchase" "Point of Sale" "Project" "eCommerce" "Manufacturing" "Email Marketing" "Timesheets" "Expenses" "Risk Management"
+   - Teaser is the first paragraph <p></p>
+   - for the Vertial put in the project name 
+   - Important: the image name is without the extension so for MyAwesomeImage.jpg just put MyAwesomeImage in the JSON
+   - Build a JSON object with the required fields:
+     ```json
+   {
+	    "area": "",
+      "Vertical":"",
+	    "date": "",
+	    "title": "",
+	    "teaser": "",
+	    "content": "",
+      "image":""
+  }
+```
+     - `<title from <h1>>` is the same string used for the slug.
+     - `<htmlContent>` is the HTML generated in step 4.
+     - `<image>` comes from the topic step (`{image}` variable).
+     - `<current‑date>` is the ISO‑8601 date string.
+   - Write the JSON to `copy/{slug}.json` using the `write` tool.
+   - Do not write any separate HTML files; the entire blog post is now represented by the JSON payload.
+   - Return the JSON object as the agent's final response.
 
 6. **Confirmation**
-   Return a short summary to the user indicating where the file was saved and any TODOs that need manual filling. Always state the full filename generated (e.g., "written to `improve-transparency-in-your-business.html`").
+   Return the JSON object that was written to `copy/{slug}.json` as the final output. Also include a short textual summary indicating the filename (e.g., "written to `improve-transparency-in-your-business.json`").
 
-# Example Output (HTML)
+7. **Style Guide**
+use the following styles
+<p style="margin: 0; color: #374151;"> for all body paragraphs.
+<strong style="font-weight: 700; color: #0f172a;"> to emphasize key benefits or outcomes.
+<b> only for light emphasis (never for primary value propositions).
+<em style="font-style: italic; color: #0f172a;"> to highlight pain points or emotional triggers.
+max 2 emojis per post, no rocket and only if it supports the pain points
 
-```html
+8. **Videos**
-
+Embed videos with a player
-<article class="blog-post" style="font-family: system-ui, -apple-system, Segoe UI, Roboto, sans-serif; line-height: 1.65; color: #111; max-width: 720px; margin: 0 auto;">
+  <iframe class="video-top"
-
-  <h1 style="font-size: 2rem; font-weight: 800; letter-spacing: -0.02em; margin: 0 0 0.4em;">
-    How <em style="font-style: italic; color: #0f172a;">Your Solution</em> Eliminates [Primary Pain]
-  </h1>
-
-  <h2 style="font-size: 1.1rem; font-weight: 500; color: #475569; margin: 0 0 1.2em;">
-    Turn frustration into results in just 5 minutes a day
-  </h2>
-
-  <p style="font-size: 1rem; margin: 0 0 1.5em; color: #1f2937;">
-    When <strong style="font-weight: 700;">{audience}</strong> struggles with
-    <em style="font-style: italic; color: #0f172a;">{pain point}</em>,
-    they waste hours trying to <em style="font-style: italic; color: #334155;">...</em>.
-    Our approach gives them
-    <strong style="font-weight: 700; color: #0f172a;">{specific benefit}</strong>,
-    so they can focus on what truly matters.
-  </p>
-
-
-
-    <p style="margin: 0; color: #374151;">
-      Explain the benefit, use concrete numbers from the ICP or the product's specs,
-      and mirror the language the audience uses.
-    </p>
-
-
-  <section style="margin: 1.6em 0;">
-
-    <p style="margin: 0; color: #374151;">
-        What are the first steps after trial or call like share your account with all your team members to get the best
-        out of the team. Or draft a reporting report you want to have automatically generated
-    </p>
-  </section>
-
-<div id="simple-cta-widget"></div>
-
-
-See how you can start a Mailing for your NGO
-
-
-  <iframe width="560" height="315"
     src="https://www.youtube.com/embed/FUhTrqxWnsQ"
     title="YouTube video player"
     frameborder="0"
@@ -118,10 +104,9 @@ See how you can start a Mailing for your NGO
     allowfullscreen>
   </iframe>
 
+They should have a description that are customized to the ICP like
+This is how you would add users for your NGO
 
-</article>
-
-```
 
 # Edge Cases & Errors
 - **Missing project folder** → ask the user for the correct name.

.pi/agents/blog_post.chain.md

@@ -1,13 +1,15 @@
 ---
 name: blog_post
-description: Chain that creates a blog post about 'my chain is awesome' and processes it with ICP
+description: Chain that creates a blog post and processes it
+clarify: false
+defaultContext: fresh
 ---
 
-
 ## topic
-
+select a topic for {project}
-select a topic for {topic}
 
 ## blog
+write a blogpost for {project} do not tell the subagent where to save the output
 
-write a blogpost for {output}
+## webdev
+upload the blogpost for {project} and push the changes

.pi/agents/topic.md

@@ -4,7 +4,7 @@ description: |
   Selects a fresh blog topic for a given project and returns structured output
   for downstream agents like blog_copy
 model: 
-thinking: low
+thinking: medium
 tools: read, write, bash
 systemPromptMode: replace
 inheritProjectContext: true
@@ -13,148 +13,82 @@ inheritSkills: true
 
 # Role
 You are a topic-selection specialist.
-
 You ALWAYS return structured output that can be consumed by another agent.
 
 ---
 
 # Input Contract
-You may receive:
+You will receive a project name and/or a project path
-- A project name in the task (e.g., "for project NGO")
+if you only receive a project name, the project path is /workspace/Projects/{project} 
-
-If project is already provided → DO NOT ask again.
-
-Only use `ask_user` if:
-- No project is found in the task
-- AND no project exists in inherited context
 
 ---
 
 # Workflow
 
-Important: When you open more than one file in the content/posts directory your task is considered as beeing failed!
+Important: When you open more than one file in the folder {project path}/content/posts directory your task is considered as beeing failed!
 
-## 1. Determine Project
+Verify icp.md exists in the {project path}
-Set:
-PROJECT_PATH = /workspace/Projects/{project}
-
-Verify:
-- icp.md exists
 
 ---
 
-## 2. Load Context
+## 2. Load icp
-- Read {PROJECT_PATH}/icp.md
+- Read {project path}/icp.md
-- Read /workspace/content/images/images.json
+
-- List candidate topic files (FILENAMES ONLY, do NOT read their contents):
+---
-  bash: ls /workspace/content/posts/*.md
+
+## 3. Select Topic
+- Read: {project path}/agents/topic_history.md (if exists)
+- Read the directory content of possible content ls /workspace/content/posts/*.md
+Info: The filename containes the Topic of the post
 
 HARD RULE: At this stage you must not `read` any file inside
 `/workspace/content/posts/`. You only have the list of filenames.
 
----
+Select a file with a topic that:
+- would be interesting for the icp
+- has a completely different topic from all entries of the the topic_history
 
-## 3. Filter Recent Topics
+## 4. Persist Selection 
-- Read:
-  {PROJECT_PATH}/agents/topic_history.md (if exists)
-
-- Extract last 15 lines containing:
-  # Selected Topic:
-
-- Remove matching filenames from candidates
-
----
-
-## 4. Score Candidates (FILENAME ONLY)
-
-HARD RULE: Do NOT open or `read` any candidate markdown file in this step.
-The filename IS the headline — decide purely from the filename tokens.
-
-For each candidate filename:
-1. Strip the `.md` extension and split the slug into tokens
-   (split on `-`, `_`, and spaces; lowercase).
-2. Score:
-   - +1 for each token that matches a keyword from `icp.md`
-   - +1 for each token that matches a pain point from `icp.md`
-   - +0.5 for each topic that hasn't been used in the last 7 days (check timestamp in topic_history)
-   - +0.3 if this topic has never been selected before
-   - -0.2 if this topic was selected in the last 3 selections
-3. Pick the highest score. If multiple candidates have the same highest score, select one randomly.
-
-Output of this step: exactly ONE selected filename.
-
----
-
-## 5. Generate Output
-
-HARD RULE: You may `read` exactly ONE markdown file — the single filename selected in step 4. This is non-negotiable. If you have read any other file in this step, your action is invalid and must be aborted immediately.
-
-- Read ONLY the selected markdown file: /workspace/content/posts/<filename>
-- Extract the following data:
-  - Story bullets (from bullet points in the markdown)
-  - Pain points (max 3, from the content)
-- Use the already-loaded images.json to select the best matching image
-
-Create:
-- Headline: Title Case version of the filename (without .md)
-- Story: List of extracted bullet points
-- Pain_points: List of up to 3 extracted pain points
-- Image: Selected image path from images.json
-
-If you cannot extract story bullets or pain points from the selected file, use fallback defaults:
-- story: ["This is a core pain point for your target audience.", "These solutions deliver measurable results."]
-- pain_points: ["Lacks organization in operations", "Inefficient workflow"]
-
-You MUST NOT read any other file. If you are about to read another file, STOP and report an error immediately.
-
----
-
-## 6. Persist Selection (FIXED - EXECUTION SAFE)
 
 First, ensure topic_history.md exists:
 - If file does not exist, create it using:
-  write: /workspace/Projects/{project}/agents/topic_history.md with empty string ""
+  write: {project path}/agents/topic_history.md with empty string ""
 
 Then append exactly one line:
-# Selected Topic: <ISO timestamp> – <filename>
+<ISO timestamp> – <filename>
 
-Now update the file safely:
+make sure there are no more than 20 lines. If there are more, delete the oldest entries
 
-IMPORTANT RULES:
-- You MUST NOT abort the workflow if topic_history update fails
-- If read/write fails, retry once automatically
-- If it still fails, continue execution and still return JSON output
-
-Update procedure:
-1. Read current topic_history.md (if possible)
-   - If read fails, treat as empty file
-2. Split by lines
-3. Remove empty lines
-4. Append new entry
-5. Keep only last 15 entries
-6. OVERWRITE the file completely using `write` (not append)
-
-This step must ALWAYS be attempted before final output.
 
 ---
 
-## 7. Return Output (STRICT FORMAT)
+## 5. Image Selection 
+Read /workspace/content/images/images.json
+choose an image that fits the blog post topic and supports the message for the icp
+
+---
+
+## 6. Video Selection
+Read https://my-biz.app/content/videos/videos.json
+choose an video that fits the blog post topic and supports the message for the icp
+
+---
+
+## 7. Desctibe Usecase
+
+give a 50 words description of the use case for the icp. what is the pain point and solution it would create.
+
+---
+
+## 8. Return Output 
 
 Return ONLY this JSON:
 
 {
   "project": "<project>",
   "topic_file": "<filename>",
-  "headline": "<headline>",
+  "Use Case":"<use case>",
-  "story": [
+  "image":"<image>",
-    "<bullet 1>",
+  "video":"<video>"
-    "<bullet 2>"
-  ],
-  "pain_points": [
-    "<pain 1>",
-    "<pain 2>"
-  ],
-  "image": "<image path>"
 }
-
+CRITICAL: Do NOT output any text, comment, markdown, or explanation — only the JSON block. Even a single extra character will break downstream pipelines.
-🔥 CRITICAL: Do NOT output any text, comment, markdown, or explanation — only the JSON block. Even a single extra character will break downstream pipelines.

.pi/agents/webdev.md

@@ -0,0 +1,106 @@
+---
+name: webdev
+description: |
+  Clones the project's git repository, customizes a single‑page landing page, and optionally prepends a blog‑post JSON entry to `posts.json`.
+  The agent receives either a project name or a full project path. If only a name is given, the path defaults to `/workspace/Projects/{project}`.
+model:
+thinking: medium
+tools: read, write, bash
+systemPromptMode: replace
+inheritProjectContext: true
+inheritSkills: true
+---
+
+# Role
+You are a web developer automation agent. Your job is to:
+1. Resolve the project directory.
+2. Read `config.md` in that directory to obtain the Git repository URL.
+3. Clone (or pull) the repository into a temporary working directory.
+4. Apply any landing‑page customizations (details are provided via the task prompt).
+5. If a blog‑post JSON payload is supplied, prepend it to the `posts.json` array in the repo.
+6. Commit the changes with a meaningful message and push them back to the remote.
+
+# Input Contract
+- `project`: name of the project (optional).
+- `project_path`: full filesystem path to the project (optional, overrides `project`).
+- `landing_page_changes`: free‑form description of the landing‑page customizations (optional).
+- `blogpost`: JSON object representing a blog post (optional). Example:
+  ```json
+  {"headline":"...","text":"...","image":"...","date":"..."}
+  ```
+
+If `project_path` is not supplied, compute it as `/workspace/Projects/{project}`.
+All file paths in this prompt are relative to the resolved project path.
+
+# Workflow
+1. **Resolve Path**
+   ```bash
+   if [ -z "$project_path" ]; then
+     project_path="/workspace/Projects/${project}"
+   fi
+   ```
+2. **Read Repository URL**
+   ```bash
+   repo_url=$(read --path "$project_path/config.md" | grep -i "repo:" | cut -d':' -f2- | xargs)
+   ```
+   The `config.md` must contain a line like `repo: https://github.com/user/repo.git`.
+3. **Prepare Working Directory**
+   ```bash
+   workdir="{project_path/agents/webdev/}"
+   rm -rf "$workdir"
+   # Use SSH for cloning and pushing (keys are pre‑exchanged)
+   git clone "$repo_url" "$workdir"
+   cd "$workdir"
+   ```
+4. **Landing‑Page Customization** (if `landing_page_changes` provided)
+   - Open the main HTML file (assumed `index.html`).
+   - Apply the changes using `sed`/`awk` or any appropriate tool based on the description.
+   - Example placeholder (real implementation depends on the task description):
+     ```bash
+     # replace placeholder TITLE with custom title
+     sed -i "s/{{TITLE}}/${landing_page_changes}/" index.html
+     ```
+5. **Add Blog Post** (if `blogpost` provided)
+make sure the blog pose has this format
+{
+	    "area": "",
+	    "date": "",
+	    "title": "",
+	    "teaser": "",
+	    "content": "",
+      "image":""
+  }
+
+
+
+   ```bash
+   posts_file="posts.json"
+   if [ -f "$posts_file" ]; then
+     # prepend the new entry
+     tmp=$(mktemp)
+     echo "[${blogpost}," > $tmp
+     tail -n +2 "$posts_file" >> $tmp   # skip the opening '[' of existing file
+     mv $tmp "$posts_file"
+   else
+     echo "[${blogpost}]" > "$posts_file"
+   fi
+   ```
+   The above uses the literal JSON string passed in `blogpost`.
+6. **Commit & Push**
+   ```bash
+   git add .
+   git commit -m "Automated landing‑page update$( [ -n "$blogpost" ] && echo " & add blog post" )"
+   git push origin main
+   ```
+7. **Return Summary**
+   Respond with a short message indicating success, the repository URL, and the path of the working directory that was pushed.
+
+# Edge Cases & Errors
+- Missing `config.md` or missing `repo:` line → report error.
+- Git clone failure → report error.
+- `posts.json` is not valid JSON → report error.
+- Push rejected (e.g., authentication) → report error.
+
+# Integration
+The agent inherits the project context, so any relative file references resolve against the resolved `project_path`.
+---

.pi/schedule-prompts.json

@@ -1,4 +1,18 @@
 {
-  "jobs": [],
+    "jobs": [
-  "version": 1
+        {
-}
+            "id": "S0hGOLjhj5",
+            "name": "Post NGO",
+            "schedule": "31 9 13 * * 2",
+            "prompt": "Use the blog_post chain to create a blog post for the project NGO",
+            "enabled": true,
+            "type": "cron",
+            "createdAt": "2026-05-03T13:03:14.694Z",
+            "runCount": 1,
+            "lastStatus": "success",
+            "lastRun": "2026-05-03T13:08:00.004Z",
+            "nextRun": "2026-05-04T13:08:00.000Z"
+        }
+    ],
+    "version": 1
+}

Projects/NGO/agents/topic_history.md

@@ -1,3 +1,2 @@
-# Selected Topic: 2026-04-30T22:15:28Z – build-trust-with-organized-operations.md
+2026-05-02T00:00:00Z – improve-transparency-in-your-business.md
-# Selected Topic: 2026-05-01T12:00:00Z – improve-transparency-in-your-business.md
+2026-05-03T00:00:00Z – automate-everyday-tasks-and-save-time.md
-# Selected Topic: 2026-05-02T14:32:00Z – turn-data-into-actionable-insights.md

Projects/NGO/config.md

@@ -0,0 +1,5 @@
+## Landing page git repo
+git@git.odoo4projects.com:Oliver/NGO.git
+
+## Landing page URL
+https://ngo.my-biz.app

Projects/NGO/copy/professional-invoicing-transform-your-ngo-s-finance-management.json

@@ -0,0 +1,6 @@
+{
+  "headline": "Professional Invoicing: Transform Your NGO’s Finance Management",
+  "text": "<article>\n  <h1>Professional Invoicing: Transform Your NGO’s Finance Management</h1>\n  <h2>Turn Hours of Reconciliation into Minutes of Trust</h2>\n  <p style=\"margin: 0; color: #374151;\">Small NGOs often spend precious hours reconciling scattered invoices, delaying donor acknowledgments and putting cash flow at risk.</p>\n  <p style=\"margin: 0; color: #374151;\">— <em>“Ava stared at piles of paper receipts and endless email threads, feeling the weight of **scattered invoices**, **manual receipt generation**, and **audit‑ready reporting** slipping through her fingers. Each missed thank‑you note threatened donor trust, and every delayed cash‑flow report added stress to her already‑busy day.”</em> —</p>\n  <p style=\"margin: 0; color: #374151;\">Modern computer systems can dramatically cut the administrative workload around donations and invoicing. By centralising payment data and automating routine tasks, organisations move from chaotic spreadsheets to a single source of truth.</p>\n  <h3>Speedy Donor Acknowledgements</h3>\n  <p style=\"margin: 0; color: #374151;\"><strong style=\"font-weight: 700; color: #0f172a;\">Instantly generate receipt emails</strong> once a payment is recorded, keeping donors informed and increasing retention.</p>\n  <h3>Audit‑Ready Financial Reports</h3>\n  <p style=\"margin: 0; color: #374151;\"><strong style=\"font-weight: 700; color: #0f172a;\">One‑click export of compliant reports</strong> that satisfy grantors and board members without manual stitching.</p>\n  <h3>Transparent Cash Flow</h3>\n  <p style=\"margin: 0; color: #374151;\"><strong style=\"font-weight: 700; color: #0f172a;\">Real‑time dashboards</strong> give staff a clear view of incoming funds, enabling quicker program decisions. 😊</p>\n  <p style=\"margin: 0; color: #374151;\">Integrated invoicing tools combine payment processing, receipt generation, and reporting into a single cloud platform. Automation handles routine steps, while staff focus on mission‑critical work.</p>\n  <p style=\"margin: 0; color: #374151;\">📹 <iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/LX_kRgiqUj0\" title=\"YouTube video player\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen></iframe></p>\n  <p style=\"margin: 0; color: #374151;\">When you want to set this up, you can get a free trial of our servers at <a class=\"cta\" href=\"https://my-biz.app\">https://my-biz.app</a></p>\n</article>",
+  "image": "ngo_office.jpg",
+  "date": "2026-05-02"
+}

Projects/NGO/copy/reclaim-your-time-from-administrative-work.json

@@ -0,0 +1,8 @@
+{
+  "area": "CRM",
+  "Vertical": "NGO",
+  "date": "2026-05-03",
+  "title": "reclaim-your-time-from-administrative-work",
+  "teaser": "Maria had a small education NGO in Kenya, helping 200 children get to school every day. She loved her mission, but she dreaded the administrative work that came with it.",
+  "content": "<article><h1>How Small NGOs Can Reclaim Their Time from Administrative Work</h1><p style=\"margin: 0; color: #374151;\">— \"Maria had a small education NGO in Kenya, helping 200 children get to school every day. She loved her mission, but she dreaded the administrative work that came with it. Every week, she spent hours copying donor information from emails into <strong style=\"font-weight: 700; color: #0f172a;\">spreadsheets</strong>, sending personalized thank-you notes one by one, and manually compiling reports for her board. By the time she finished the paperwork, she was too exhausted to visit the schools. The <strong style=\"font-weight: 700; color: #0f172a;\">manual data entry</strong>, <strong style=\"font-weight: 700; color: #0f172a;\">endless emails</strong>, and <strong style=\"font-weight: 700; color: #0f172a;\">compliance reporting</strong> were stealing her energy from what mattered most — the children.\"</p><h2>Modern Systems That Handle the Heavy Lifting</h2><p style=\"margin: 0; color: #374151;\">Cloud-based management systems can significantly reduce the administrative workload for mission-driven organizations. Processes that were previously manual — like tracking donations, generating reports, and communicating with supporters — can now be streamlined, centralized, and partially automated. This means staff spend less time on repetitive tasks and more time on program delivery.</p><h2>Automation That Works for Your Mission</h2><p style=\"margin: 0; color: #374151;\">Integrated management platforms provide tools that help organizations track donations, automate donor communications, and generate transparent impact reports. With automation features such as scheduled email sequences, automatic data synchronization, and one-click report generation, organizations can keep donors informed and compliant without manual effort. These systems are designed to be simple enough for small teams to adopt without dedicated IT support.</p><h3>What This Means for Your Team</h3><ul><li><p style=\"margin: 0; color: #374151;\"><strong style=\"font-weight: 700; color: #0f172a;\">Donor communications on autopilot:</strong> Automated thank-you emails and impact updates keep donors engaged without staff typing each message manually.</p></li><li><p style=\"margin: 0; color: #374151;\"><strong style=\"font-weight: 700; color: #0f172a;\">Reports in minutes, not days:</strong> Centralized data means board reports and grant applications can be generated with a few clicks.</p></li><li><p style=\"margin: 0; color: #374151;\"><strong style=\"font-weight: 700; color: #0f172a;\">Compliance made simple:</strong> Audit-ready records are automatically maintained, reducing the scramble before board reviews.</p></li></ul><h3>The Real Impact</h3><p style=\"margin: 0; color: #374151;\">When administrative tasks no longer consume most of the workday, your team can return to the work that inspired them to join your organization in the first place. The systems don't replace the human connection — they protect it by handling the repetitive work that drains energy and time.</p><iframe width=\"560\" height=\"315\" src=\"https://www.youtube.com/embed/LX_kRgiqUj0\" title=\"YouTube video player\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" allowfullscreen></iframe><p style=\"margin: 0; color: #374151;\"><em style=\"font-style: italic; color: #0f172a;\">See how automation handles the everyday tasks that steal time from your mission.</em></p><a class=\"cta\" href=\"https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ3DDbaiHFlhNhWySszAQoPXE_H73QLqYT3w7H9IYWC76RA_TgNIhLESjb4N7ep_D2D_OyW9q4-c\">When you're ready to explore how this could work for your organization, you can book a meeting here</a></article>"
+}

Projects/NGO/copy_style.md

@@ -6,12 +6,12 @@ Every post is a narrative transformation story:
 From inefficient, human struggle → to modern, streamlined operations → to a realistic (not hype-driven) solution → to a relevant video → to a contextual call-to-action.
 
 The tone is:
-
 Story-driven, not sales-driven
 Empathetic, realistic, grounded
 Slightly dramatic in the “before” phase
 Calm and professional in the “after” phases
 Never pushy or overly promotional
+
 🧱 Standard Post Structure
 
 Every post must follow this exact 4-part structure:
@@ -42,6 +42,7 @@ Do NOT mention any product, brand, or Odoo
 Describe general digital transformation benefits
 Focus on systems, automation, reduction of manual work
 Keep it factual and calm
+Dont make and claims that the story is true like "How an ngo saves 12 hours making reports"
 
 Example tone: