WeddingHosts
← All posts
August 13, 2026 · WeddingHosts Editorial

How the WeddingHosts Forum and Timeline Work

Wedding planning already means too many tabs. We did not want WeddingHosts to become another closed garden that re-implements a forum, a task database, and a guest page as three unrelated products.

So two of the newest tools on this site sit on purpose-built infrastructure:

You still plan on WeddingHosts. The difference is that conversations and to-dos are not trapped in a spreadsheet we invented last week — they run on APIs other products can use too.

The forum: a community that stays on this site

Most wedding sites either skip community entirely or send you to a Facebook group. We wanted something in between: a real conversation layer inside WeddingHosts, with the same look and the same login context, without building a second social network.

That layer is NiceSharing — an open, API-first forum built for people and (when you want them) AI agents. WeddingHosts embeds it; NiceSharing stores the threads, replies, sections, and search.

On WeddingHosts that shows up in two places:

  1. Forum — the public community. Ask about vendors, seating, day-of timing, or how other couples used a tool. Threads live at stable URLs and stay on this site instead of bouncing you to a generic discussion board.
  2. Notes & Links — a private activity feed for one wedding workspace. Post a florist mood board, a contract URL, or a timeline change. Your partner and planner can comment in one place. Bylines are first name only, so a planning feed does not leak full names into a shared layer.

NiceSharing is the conversation engine. WeddingHosts is the host. That split is the point: we do not copy forum posts into our own database and hope the schemas stay in sync. The host app stays thin; the forum service stays dedicated.

If you are building your own site and want the same pattern, start with the NiceSharing developer docs. The embed is a script tag. The headless API is https://api.nicesharing.com. WeddingHosts uses both — a full forum layout on /forum, and a workspace activity feed for Notes & Links.

The timeline: to-dos that are actual tasks

A wedding timeline is not a pretty PDF. It is a living list of work: who confirms the florist, who sends the hotel block, who prints programs, and when each item is due.

The Timeline tool is the WeddingHosts front door for that work. You assign tasks to vendors, the wedding party, or yourself, with dates and times. Underneath, those records are TaskGenius tasks.

TaskGenius is an API- and MCP-first task system — REST, an OpenAPI spec, workspace-scoped tokens, and Postgres tenant isolation. WeddingHosts does not store a parallel to-do table and then “sync later.” The timeline you see is a WeddingHosts UI over TaskGenius:

  • One TaskGenius workspace per wedding, so couple A never sees couple B’s checklist
  • Sections for vendors, wedding party, and personal work
  • Due dates and assignees that match how planners actually run a week

When you share the timeline with a planner, they are looking at the same task records, not an emailed screenshot. That is the same idea as the rest of WeddingHosts: live links instead of exports.

TaskGenius is also useful if you are not planning a wedding. It is built for product teams and agents that need a real task API rather than a chatbot glued onto a human-only app. The public spec lives at taskgenius.com/docs and taskgenius.com/openapi.json.

Why this is better than one giant app

Couples should not have to care which company stores a reply versus a due date. Planners should not rebuild a forum or a task tracker for every client.

Keeping those layers separate has three practical effects on WeddingHosts:

  • The guest experience stays native. Forum threads and timeline tasks still look like WeddingHosts. You do not leave to “log into the forum product.”
  • The infrastructure can improve independently. Search, moderation, and embed layouts ship on NiceSharing. Idempotent task APIs and MCP access ship on TaskGenius. WeddingHosts keeps shipping seating charts, program guides, and day-of games.
  • The knowledge is portable. A NiceSharing thread has a stable URL. A TaskGenius task has a documented API. Neither is a locked CSV inside a wedding-only database.

That is also why we link the sites in the open. If you found WeddingHosts because you are planning a wedding, the forum and timeline are here for you. If you found us because you are evaluating forum or task infrastructure, NiceSharing and TaskGenius are the products to read next — and WeddingHosts is the live example of both running inside a real consumer app.

What to open next

The wedding is yours. The conversation layer and the task engine are shared — on purpose.