ChabadOne Integration

ChabadOne is the platform most Chabad Houses run their websites on. It requires XHTML 1.0 compliance, which collides head-on with the HTML5 and inline-script habits of modern AI code generation. The chat has documented several workable patterns.

The XHTML compatibility wall

"If you want to embed AI-generated code, it has to be XHTML 1.0 to be fully compliant with ChabadOne and not get the XML error screen."

Pattern 1: Claude artifact plus iframe

The workaround:

1. Ask Claude to create a rich website with no limits or rules using HTML5.
2. Click Publish on the artifact (top right).
3. Click Get embed code, enter your domain, copy the embed <iframe> code.
4. Create a new web doc on ChabadOne; paste the <iframe> code.
5. Optional: in ChabadOne's advanced options, expand body to full width and hide template for a cleaner browsing experience.

Warning: the artifact is public on Claude. Don't use this for anything sensitive.

Pattern 2: Tell the AI about ChabadOne's constraints

Feed the AI ChabadOne's HTML help article plus your design intent, and ask one model to write a prompt for another model that respects the constraints:

"Feed the AI the ChabadOne help article with HTML guidelines (search 'HTML'). Ask one AI to create a prompt for another AI based on ChabadOne guidelines and your design ideas. Tell AI you need code that is 'xhtml 1.0' compatible."

Then iterate: generate, test inside ChabadOne, and ask the AI to fix what breaks. "Have AI summarize what worked / didn't work. Create a brief prompt with guidelines. Use going forward as parameters for building other pages."

Pattern 3: The Universal ChabadOne Page Builder prompt

A platform-agnostic system prompt that works with Claude, ChatGPT, or Gemini:

• Paste the contents into a fresh conversation.
• The AI asks: CREATE NEW PAGE versus MODERNIZE EXISTING PAGE.
• If modernizing, paste the existing HTML; the AI extracts the content first, then only asks for what it can't figure out.
• Content sourcing is hardcoded to orthodox sources: Chabad.org, Sefaria, Aish.com, OU, YU Torah, and classical texts.
• Output: clean, mobile-responsive HTML for ChabadOne.

The prompt itself is shared on shluchimexchange.ai. See Master Prompts for a copy.

Pattern 4: Minisites via Manus.im plus ChabadOne articles

1. Use AI to draft a prompt for Manus.im to scan Chabad.org for content (specify your audience and topic).
2. Take Manus's report back to your AI; add your event info; have it generate HTML for a one-page site (flyer placeholder plus RSVP button).
3. Specify design preferences (colors, layout, nav bar) up front.
4. Paste into ChabadOne, adjust, done.
5. Advanced: a multi-page minisite, each page a ChabadOne article, with the AI directing the nav bar to internal links.

Examples that worked:

• jewishpedro.org/templates/articlecco_cdo/aid/7260228/jewish/Passover-Minisite.htm
• jewishpedro.org/templates/articlecco_cdo/aid/7260225/jewish/Purim-Minisite.htm

Pattern 5: Squarespace plus ChabadBrand (alternative to ChabadOne)

For shluchim who give up on ChabadOne styling, the consensus alternative is Squarespace with ChabadBrand templates, examples being chabadfortwayne.com and jewishchagrinfalls.com, on a Squarespace account at $30/month: more design freedom, no XHTML constraint.

What ChabadOne doesn't have (yet)

The group's recurring wishlist:

• Native SMS RSVP. The most-voted missing feature. Workarounds via Lovable plus Twilio.
• Real dynamic CRM integration. ChabadOne is on Salesforce, so MCP works; see CRM Automation.
• AI agent to auto-update the site. Periodically proposed.

Related

• ShluchimExchange.ai, which has a ChabadOne CSS code agent.
• Master Prompts, the full universal page-builder prompt.
• Flyer Design, because flyers eventually need to land here.
• CRM Automation, the Salesforce-backed CRM.
• Vibe Coding, why some shluchim sidestep ChabadOne entirely.