UAD 3.6 Wiki — Session Notes & Recommendations

Date: 2026-06-28 | Project: True Footage UAD 3.6 Knowledge Base


Project Summary

Fully designed UAD 3.6 knowledge base — all content written, Drive folder structure mapped, 7 Apps Scripts ready to deploy, Google Sites framework documented. Status: Not yet deployed. Everything exists as local files at C:\Users\kzele\Claude Cowork\Projects\UAD 3.6 Wiki\.

Package Contents

Component Status
12 wiki content markdown files ✅ Complete
7 Apps Scripts (Drive scaffolding) ✅ Ready to run
Google Sites implementation guide ✅ Complete
Sites HTML page templates ✅ Complete
AI build prompt (Gemini/Antigravity) ✅ Complete
3 source PDFs ✅ Present

Assessment

What's Working Well

  • Content is solid and specific — field IDs, Selling Guide SB-series citations, audience-split FAQs
  • Apps Scripts automate ~80% of the mechanical build work
  • 12 wiki content files cover the full UAD 3.6 scope
  • Maintenance procedures defined and realistic

Problems / Gaps

1. Google Sites is the wrong tool for this content type. Sites is a landing page builder, not a wiki. No version history per page, no inline commenting, no structured search beyond basic text matching, no content ownership enforcement, no staleness alerts. For 100+ appraisers using this daily, those gaps matter.

Fix: Maintain one master index Google Sheet (already in your structure as the Field ID index) and embed it on the home page with filtering. That becomes the searchable entry point, not Sites search.

2. Apps Scripts won't survive a re-run without manual ID updates. Scripts hardcode PARENT_FOLDER_ID — every script requires manual variable updates before running. One wrong ID breaks the link chain (Form → Sheet, Doc → Folder). No validation or rollback.

3. Content is static markdown not yet in Drive. 07_PopulateContentDocs.gs hits the 6-minute Apps Script timeout. Large sections (FAQ, Inspection/Reporting) will require multiple re-runs.

Fix: Split 07_PopulateContentDocs.gs into per-section scripts or use time-based triggers to restart automatically.

4. No update pipeline. When Fannie/Freddie push Supplement revisions (the June 3, 2026 PDF already superseded earlier versions), there's no mechanism to push changes into the wiki.

5. Key Links table is blank. The Implementation Guide has [paste after publishing] placeholders — wiki isn't deployed yet.


Architecture Recommendation

Drive → Google Sites → NotebookLM

Since most content will be created within Google Workspace/Drive:

  • Drive — source of truth, where content is created and edited
  • Google Sites — structured navigation layer (auto-reflects Drive edits via live embedding)
  • NotebookLM — Q&A layer connected to the Drive folder as a live source (auto-ingests new Docs as they're created)
  • FAQ Sheet — structured search backbone for field IDs and cross-references

No new tools, no licensing, fully Google Workspace-native, scales with content volume.

NotebookLM supports Google Drive as a live source — connect the wiki Drive folder and it ingests Docs automatically. As your team adds content, NotebookLM stays current without manual uploads.


Landing Page: Better Options Within Google Ecosystem

Google Sites has significant design constraints. Better path:

Gemini generates → Firebase Hosting publishes

Both Google products, free, no design ceiling. The Sites wiki becomes the deep navigation layer; Firebase hosts the polished entry point.

Gemini Landing Page Prompt (ready to paste into AI Studio)

You are an expert web designer. Build a complete, self-contained HTML landing page for an internal knowledge base called the "UAD 3.6 Wiki" used by residential appraisers at True Footage, a nationwide appraisal firm.

## Requirements

### Design
- Clean, professional, modern design — think Google Material Design 3 or Notion-style
- Color palette: deep navy (#1a2744) primary, white (#ffffff) background, amber (#f59e0b) accent for urgency/CTAs, light gray (#f8f9fa) card backgrounds
- Font: Google Fonts — Inter for body, Inter for headings (include the @import)
- Fully responsive (mobile-first)
- No external JS libraries — vanilla JS only
- All CSS inline in a <style> block — single self-contained file

### Header / Hero
- Site title: "UAD 3.6 Knowledge Base"
- Subtitle: "Your reference for UAD 3.6 compliance, field definitions, and appraiser guidance"
- Prominent amber banner: "⚠️ Mandatory adoption deadline: November 2, 2026"
- Search bar (visual only — no backend needed, placeholder text: "Search fields, topics, FAQs...")

### Navigation Cards (12 sections — displayed as a responsive grid)
Each card has an icon (use Unicode emoji), title, and one-line description:

1. 📋 UAD 3.6 Overview — What changed from UAD 2.6, timeline, glossary
2. 📄 URAR Form & Field Reference — Section-by-section field guide and enumeration values
3. 🏠 Condition & Quality Ratings — C1–C6 and Q1–Q6 definitions, decision trees
4. 🔍 Inspection & Reporting — Tips by URAR section, new data collection requirements
5. ✅ Property Eligibility — GSE eligibility rules, ADUs, leasehold, disaster properties
6. 📊 Valuation & Comparables — Sales comparison, adjustments, dynamic grids
7. 📁 Appraisal Types & Processes — Desktop, hybrid, value acceptance, age requirements
8. 🏭 Manufactured Housing — Eligibility, certifications, multi-unit, multi-story
9. ⚡ Special Topics — CLTs, mixed-use, environmental, renovation loans, Texas 50(a)(6)
10. 🏢 Condo, Co-op & PUD — Project standards, PERS, PUD and co-op eligibility
11. 📝 Lender Review & Quality — URAR review checklist, appraiser selection, AQM
12. ❓ FAQ — General, appraiser, lender/underwriter, and transition FAQs

Cards should be clickable (href="#" placeholder). Hovering a card should lift it slightly with a subtle shadow transition.

### Quick Links Bar
Below the nav grid, a horizontal row of high-priority links:
- "Submit a Question" (links to #, styled as amber button)
- "Field ID Index" (links to #)
- "UAD 2.6 → 3.6 Cross-Reference" (links to #)
- "Source Documents" (links to #)
- "Fannie Mae UAD Page" (links to https://singlefamily.fanniemae.com/delivering/uniform-mortgage-data-program/uniform-appraisal-dataset)
- "Freddie Mac UAD Page" (links to https://sf.freddiemac.com/tools-learning/uniform-appraisal-dataset)

### What's New Section
Below quick links — a "What's New" panel with 3 placeholder entries styled as a timeline or feed:
- [2026-06-03] UAD 3.6 Supplement updated — Section 5 and 8 revisions
- [2026-03-31] ADU expanded eligibility effective — multi-unit and MH Advantage
- [2026-01-25] Limited Production Period ended
Include a "View full change log →" link.

### Footer
- "True Footage | Internal Use Only"
- "Content questions? Contact [wiki admin]"
- "Last updated: June 2026"

## Output
Return ONLY the complete HTML file. No explanation, no markdown fences, no commentary. Start with <!DOCTYPE html>.

Firebase Hosting Deploy Steps

npm install -g firebase-tools
firebase login

mkdir "C:\Users\kzele\Claude Cowork\Projects\UAD 3.6 Wiki\firebase-hosting"
cd "C:\Users\kzele\Claude Cowork\Projects\UAD 3.6 Wiki\firebase-hosting"
firebase init hosting
# → select project, public dir = public, single-page app = No

# Drop Gemini HTML output into public/index.html, then:
firebase deploy --only hosting
# Result: https://your-project.web.app

Access control: Firebase Hosting is public by default. For internal-only access, share the URL privately via Slack/Teams. The wiki contains no GLBA-protected NPI — UAD policy content has no data risk.


Immediate Next Steps (Priority Order)

  1. Pick a Drive parent folder → run script 01_CreateDriveFolders.gs today
  2. Run scripts 02–06 in sequence
  3. Fix timeout risk in 07_PopulateContentDocs.gs before running it (split by section)
  4. Start Sites build using google-sites/SitesImplementationGuide.md
  5. Create NotebookLM notebook, connect the wiki Drive folder as a live source
  6. Paste Gemini landing page prompt into AI Studio, generate HTML, deploy to Firebase

The content is ready. This is a deployment problem now, not a design problem.


Key Dates

Date Event
2026-06-03 UAD 3.6 Supplement updated (Section 5 and 8 revisions)
2026-03-31 ADU expanded eligibility effective
2026-01-25 Limited Production Period ended
2026-11-02 Mandatory UAD 3.6 adoption deadline (all UCDP submissions)

Session notes — 2026-06-28 | True Footage internal use only