Nudger User Guide: End-to-End QA and Automation

1. Executive Summary

https://docs.google.com/presentation/d/1V_B4w1fQSqsPepETmuC1JutgX_JhRjFakkav6p7xNSI/edit?usp=sharing

What is Nudger?
Nudger is an automated project management and Quality Assurance (QA) layer designed to sit directly on top of Trello. Its primary purpose is to streamline the lifecycle of new landing pages and web projects (typically denoted by PFxxxx Trello cards), ensuring that nothing falls through the cracks from the initial brief to the final live deployment.

How it sits atop Trello:
Nudger acts as a continuous sync engine. It monitors specific Trello lists (To Do, In Progress, Review, etc.) and automatically reads card attachments, comments, and custom fields. If a stakeholder forgets to attach a design brief or a Figma file, Nudger detects the omission and allows the admin "nudges" them via Slack.

How it uses AI:
Nudger heavily leverages AI to reduce manual data entry and QA setup:

  • Brief Parsing: It reads .odt design briefs attached to Trello cards and uses an LLM (Llama-3) to automatically extract the required page sections, the expected copy, and Call-to-Action (CTA) details.
  • Compliance Scanning: It uses AI to scan page previews, checking for compliance, required legal text, and missing tracking tags.

2. The Project Lifecycle (To Do → Done)

Nudger tracks projects as they move through your Trello board. Here is how it interacts with each stage:

Stage 1: To Do

  • What it means: The project has been created, but development hasn't started.
  • Nudger's Role: Nudger ensures the foundation is solid. It checks the Trello card for a valid Design Brief (.odt), a Figma link, and a due date. If any of these are missing and the due date is approaching (less than 10 days), Nudger will automatically alert the relevant stakeholders on Slack to supply the missing assets.

Stage 2: In Progress

  • What it means: The tech team is actively building the landing page.
  • Nudger's Role: Nudger expects preview URLs to be generated. The team can start using the AI Scanner to build the preliminary QA checklist based on the design brief. Nudger continues to track the timeline, issuing warnings if the project is close to the deadline.

Stage 3: Growth Review

  • What it means: Tech has finished the initial build; the Growth team is reviewing for sign-off.
  • Nudger's Role: Nudger verifies that the page matches the brief. If Growth signs off or requests changes via Trello comments, Nudger ensures the right developer is notified.

Stage 4: Tech Review

  • What it means: Growth has signed off, and the tech team is doing a final internal audit.
  • Nudger's Role: This is where the QA Bot shines. The QA team runs the automated visual and functional tests (see Section 4) to ensure the page is pixel-perfect, checkout links are correct, and all tracking tags are intact.

Stage 5: Tech Work Done

  • What it means: The page has passed all reviews and is ready to go live.
  • Nudger's Role: Nudger monitors the transition from a preview URL to the live production URL. It reminds the tech team to push the page live if the due date has arrived.

Stage 6: Done

  • What it means: The project is complete and live.
  • Nudger's Role: The project is ready to be promoted to the Aegis Admin system for continuous daily monitoring.

3. The AI Scanner

The AI Scanner is Nudger's automated setup assistant for QA.

How it works:

  1. When you click "✨ Run AI Scanner" on a project, Nudger downloads the .odt design brief directly from the Trello card.
  2. It passes the text of the brief to a Large Language Model (LLM).
  3. The AI reads the document and structures a JSON array containing every expected section of the page (e.g., hero, image-with-text), the main copy for that section, and the expected CTA buttons.
  4. Nudger uses this structured data to automatically pre-populate the QA Bot's testing checklist, saving you from having to manually define what sections should exist on the page.

4. The QA Bot & Interactive Audit

The QA Bot is a visual testing suite embedded directly into the Nudger dashboard.

Using the QA Bot:

  • Interactive Highlighting: When you open the QA Bot for a project, it loads a live, proxy-injected preview of the page.
  • Point and Click Setup: You can visually click any element on the preview page. When clicked, it highlights the element and shows a "➕ Add to QA" button.
  • Smart Extraction: Clicking "Add to QA" automatically analyzes the section. It finds the top-level heading to name the section, extracts the text copy, and searches the section for Google Analytics tags (data-tracked="true"). It then adds this section to your QA Checklist as a new test case.
  • Test Configurations: For each section in the list, you can define the action:
    • View: Ensures the section renders correctly.
    • Click: Ensures the element can be interacted with.
    • Pixel/Checkout: Verifies marketing pixels and that Trello-supplied checkout links match the live buttons.
  • Running the Automation: Clicking "Run QA Automation" triggers the Visual Monitor. A headless browser navigates the page, takes screenshots, verifies the copy matches the brief (warning or failing if it differs), and ensures all GA tracking attributes are present.

5. Promoting to Aegis Admin

Once a project has passed all QA checks and is marked as Done (or Tech Work Done) with a valid live URL, it must be handed off to Aegis for long-term monitoring.

The Handoff Process:

  1. In the Nudger dashboard, click the "🛡️ Move to Admin" button on the completed task.
  2. Nudger packages up the entire QA configuration you just built—including the AI-extracted sections, the custom copy checks, the GA tag validations, and the expected checkout links.
  3. This configuration is seamlessly transferred to the Aegis Admin database.

Daily Page Monitoring: Once in Aegis Admin, the exact same QA tests you configured in Nudger are scheduled to run daily.

  • The Aegis visual monitor will visit the live page every day.
  • It ensures that no third-party apps or subsequent code changes have accidentally deleted a section.
  • It verifies that the checkout links haven't expired or changed.
  • It guarantees that the data-tracked="true" GA tags haven't been stripped out by a theme update.

If any of these daily checks fail, Aegis will instantly alert the tech team via Slack, ensuring long-term stability long after the Trello card has been archived.

6. Reporting and the Leaderboard

To keep the team aligned and accountable, Nudger automatically generates comprehensive reports summarizing the state of all projects.

The Daily Report:

  • What it is: A global snapshot of all active landing pages and tasks currently tracked by Nudger across the Trello board.
  • What it includes: It highlights projects that are falling behind schedule, missing crucial assets (like briefs or Figma links), or failing automated QA checks.

The Nudge Leaderboard:

  • What it is: A playful (but effective) feature embedded within the Daily Report that tracks who has been "nudged" the most.
  • How it works: Every time Nudger automatically alerts a stakeholder via Slack for missing a deadline or asset, it tallies a point against them.
  • Purpose: It serves as a lighthearted gamification tool to encourage the team to attach assets promptly and meet deadlines, displaying the "top players holding up the board." If everyone is on track, the leaderboard gracefully acknowledges that no one has been nudged.