How TaliCMS Works

Most platform pages describe features. This one describes a Tuesday.

You've got a board meeting agenda to post, three new affiliate members to add, an education class that just changed rooms, and a president's message that needs to go up before noon. Here's how each of those actually goes.

---

The short version

TaliCMS is the public website for your association. It is not your AMS — your membership records, dues, and NRDS data stay exactly where they are. TaliCMS connects to those systems, pulls in what members need to see, and gives your staff a straightforward place to publish everything else.

You log in at yourassociation.com/admin. You'll see a list of the things your site is made of — News, Events, Documents, Committees, Staff, Pages. You click one, you edit it, you hit save. The site updates. No ticket, no developer, no waiting.

That's the whole model. The rest of this page is detail.

---

1. Publishing a page

Pages are built from blocks — pre-designed sections you stack in whatever order you want. A hero banner. A block of text. A two-column text-and-image. A list of upcoming events. A grid of documents. A frequently-asked-questions accordion. A call-to-action.

You're not editing HTML and you're not fighting a page builder that lets you break the design. Each block is already styled to your association's brand, so a page you build in four minutes looks like a page your designer built. The constraint is the point: staff can't accidentally publish something off-brand.

Draft and preview. Every page has a draft state. You can build the whole thing, look at it exactly as it will appear live, send the preview link to your AE for sign-off, and publish only when they say yes. Nothing goes public until you publish it.

Version history. If someone changes something and it turns out wrong, you can see what changed and roll back. This also covers your header and footer navigation — the two things that are most frightening to edit and hardest to undo elsewhere.

---

2. Events and education

Events are the single most-visited thing on most association sites, and the most annoying to maintain.

If your association uses an events or registration feed, TaliCMS pulls it in on a schedule — your calendar populates itself, and registration links point wherever they should. Staff aren't re-typing the class list every month.

Events you run manually work the same way as any other content: create it, set the date, pick the event type, publish. It appears in the calendar, in the "upcoming events" block on the homepage, and in the related-events rail on relevant pages, automatically. You place it once.

Currently in production: Tangilla event feeds (several REALTOR® associations) and EdConnect course feeds (a statewide association).

---

3. Members, directories, and "Find a REALTOR®"

Your member data lives in your system of record. TaliCMS reads it.

That means the public directory — Find a REALTOR®, brokerage lists, affiliate lists — reflects your actual membership without staff maintaining a second copy of it. When someone joins or leaves, the directory follows. Nobody is exporting a spreadsheet on the first of the month.

What we've connected so far: NAR's M1 Gateway for NRDS member and office data, and Tangilla member and office feeds. At one statewide association that's 146,014 members and 35,951 offices syncing automatically.

Members can update the parts of their profile you let them control; the fields your association owns stay owned by your association.

---

4. Member-only content

Some things are for members: forms, legal hotline, contract templates, committee material.

TaliCMS gates that content behind whatever login your members already use. It doesn't create a new password for them to forget. At one association that's Clareity SSO — the same credentials they use for the MLS. At another it's Auth0 with NAR authentication.

The rule we work to: no member should need a second login to read a document. Separate logins are one of the most common complaints association staff hear, and it's usually a platform decision, not an inevitability.

---

5. Documents — the part nobody demos

Every association is sitting on hundreds of PDFs. Bylaws, forms, meeting minutes, market reports, policy documents. On most sites they're in a folder somewhere, findable only if you already know the name of the thing you're looking for.

TaliCMS organises documents into folders you control, with proper titles and descriptions, so they can be browsed. And at one association we've gone further: search reads inside the documents. A member searching for a phrase that appears on page 6 of a PDF will find that PDF, without knowing its filename.

If your staff spend time answering "where do I find the…" emails, this is the part of the platform that gives you time back.

---

6. Listings and market statistics

If your association wants MLS listings on the public site, TaliCMS connects to your MLS feed directly and keeps them current. We've done this three different ways for three different associations, because every MLS is different — see Your MLS Feed, Handled.

Market statistics work similarly. At one association, monthly housing reports arrive as PDFs and the platform extracts the numbers into structured data, so the site can show real charts by city and county instead of a link to a download.

---

7. Forms

Contact forms, membership applications, committee interest, event feedback, complaint submissions. You build them in the admin by dragging fields, decide where submissions go, and publish. Submissions are stored in the admin so nothing is lost in an inbox.

---

8. Knowing whether any of it worked

Your site's traffic data appears inside the admin — top pages, visitors, trends over time. Staff don't need a Google Analytics login or training to answer "did anyone read the president's message?"

---

9. What happens at launch

The part associations worry about most: what happens to everything we already have?

Before we switch anything over, we crawl and archive your existing site in full — every page, every URL, every document link. Then we map old addresses to new ones so that a member's bookmark from 2019, a link in an old email newsletter, or a page Google has indexed still lands somewhere sensible instead of a dead end.

After launch we re-crawl the new site and check every internal link, external link, and asset, and fix what's broken before anyone notices. It's unglamorous and it's the difference between a launch your members complain about and one they barely notice.

---

10. What you need on your side

Honestly: less than you'd expect, but not nothing.

• One person who owns the site. Usually the Communications or Marketing Director. Not an IT person — the platform doesn't need one.
• Decisions. Most delays in a website project are decision delays, not build delays. Who approves copy? What's staying and what's being retired?
• Your content. We migrate what exists, but a rebuild is the best chance you'll get to delete the pages nobody has opened since 2021.
• Access to your feeds. MLS credentials, AMS/member data access, event feed details. These often take longer to obtain from third parties than anything on our side — start early.

---

What it doesn't do

Being straight about the boundaries, because a vendor who won't name them is a vendor who'll surprise you later:

• It is not an AMS. It doesn't process dues, hold your membership records, or run your accounting. It connects to the system that does.
• It doesn't replace your MLS. It displays listings from your MLS feed.
• It won't write your content for you. A new platform makes publishing easy; it doesn't decide what your association should say.

---

Want to see it?

The fastest way to understand this is fifteen minutes of someone clicking through the admin while you watch, using your association's actual content as the example.