Skip to main content

​
Public posts on a project landing

A project landing can list published posts and open each one on its own URL, without asking visitors to sign in. The posts themselves stay a normal table in the project. You write and publish them in the portal (or ask the in-app AI). Guests only see rows you have marked published, and only the fields you chose to share. The same project landing can also open first on a public intake share or QR link (Public intake → Guest page first). Guests continue into the form when they are ready. This is not the same as Public Project. Public Project only lets the project’s public hosts resolve. It does not make tables world-readable.

​
What you need

  1. A project landing that is enabled, plus an active Project landing custom domain. Slug subdomains stay portal-only. See Custom domains.
  2. Public Project on (the default for new projects).
  3. A table with a unique slug, a publish flag (or publish time), and the fields guests should read.
  4. A public collection that names that table, the slug and publish columns, and the field lists.
HIPAA-enabled apps cannot use project landings or public collections.

​
How guests see it

  • / (or the list path you set) shows the about page plus published posts.
  • The public list, sitemap, and assistant list share one order. In Building, set that order on a column guests already see (a number order field or the published date). The landing already receives posts in that order.
  • /posts/your-slug (or your detail path) shows the full published post.
  • A post page can also show other published posts from the same list, for example the previous and next posts. Visitors still only see published rows and the fields you chose to share.
  • Unpublished or unknown slugs look the same to guests: not found.
  • Share previews use the published title and description when you have mapped those fields.
  • If App Settings → Appearance → Languages has more than one language, guests see the matching title when the row has a locale bag or a parallel language column. Sitemap and /llms.txt also list the prefixed URLs (/ar, /fr). See Languages.
After you change the landing design, Publish so visitors get the new look. New or updated published rows can appear without another Publish. The collection contract (which table, paths, and fields guests can read) is frozen at Publish. Marking a row published can still make it appear without another Publish. Preview → Draft on the project landing uses the draft contract so you can try an unpublished collection. To try an unpublished landing design without shipping it, open Preview, switch the surface to Project landing, and choose Draft. The public domain still shows the last published look until you publish. Crawlers and assistants can read /llms.txt and /sitemap.xml on the landing domain for the home URL plus published post links. /robots.txt points at that sitemap. Unpublished rows stay off both lists. In Google Search Console, submit the landing hostname’s /sitemap.xml, not the GenieForge marketing sitemap.

​
How you write posts

Use the portal pages and forms for that table, or Chat mode with the table’s model. Publishing is updating the publish field on a row. Drafts stay in the project and are invisible on the landing.