> ## Documentation Index > Fetch the complete documentation index at: https://docs.thefaithapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Public Church Pages > Consistent church branding, responsive navigation, and focused forms across your public church pages. # Public Church Pages TheFaithApp hosts a small public website for every church. These pages need no sign-in and are meant to be linked from your own website, social media, printed materials, and the QR code on the dashboard. ## The Pages | Page | What a visitor can do there | | -------------- | ------------------------------------------------------------------------------------------------------ | | Visit | Plan a first visit: see service times, directions, and what to expect, and submit a plan-a-visit form. | | Connect | Fill in the connect card after a service, with a message to the church. | | Devotionals | Read the church's published devotionals, filter them by topic, subscribe by email, or get the app. | | Campaigns | See active giving campaigns and give to one. | | Outreach | Learn about outreach initiatives and how to take part. | | Give | Give a one-time or recurring gift to the church's funds. | | Prayer Request | Send a prayer request to the church. | Where to manage each page's content: * Visit and Connect: **Visitors** (see [New Visitor Journey](/product/new-visitor-journey)). * Devotionals: **Devotionals** in the sidebar. * Campaigns and Give: **Giving** (see [Giving and Finance](/product/giving-and-finance)). * Outreach: **Outreach Campaigns**. * Prayer requests arrive in **Pastoral Care** and **Prayer Community**. ## The Devotionals Page * **Topics** are the tags you add to a devotional in the dashboard. They appear as chips under the search box, most used first, and a visitor taps one to filter the list. Each card also shows its topics. * **Subscribe by email** adds the visitor to **Marketing → Email Subscribers** with the source "Devotionals". Use that list to send new devotionals out. * **Get the app** appears when the church's mobile app link is configured, and opens the same store link as the dashboard QR code. ## Event Pages Each public event has its own page, linked from the dashboard's event share button. Beside the event details sits a registration card that shows how many spots are left, the date to register for, and the questions you chose to collect. At the top of the card a visitor can add the event to **Google Calendar** or download it for **Apple / Outlook**, and **Share** the page. To ask guests a yes/no question while they register, add **registration options** to the event under its registration settings, one per line, for example "Bring a dish". Each becomes a checkbox on the public page, and the guest's choices appear on their confirmation, in the occurrence workspace, and in the registrations export. ## One Header and Footer Every public page carries the same header and footer, so a visitor who arrives on the giving page can find the connect card or the devotionals without going back to your website. The header shows: * your church logo and name, which return to the Visit page; * links to Visit, Connect, Devotionals, Campaigns, and Outreach, with the current page highlighted; * a **Give** button that opens the giving page (hidden on the giving page itself); * the sign-in control, on pages that offer a member sign-in. On smaller screens, open the church menu to find the page links and **Give**. Connect cards, published forms, giving, and prayer requests use this compact menu at every screen size so visitors can focus on completing their task. The giving page does not repeat a link to itself. Published forms show the church identity in the header and one clear form title above the questions. Embedded forms keep their church identity inside the form, without adding the shared navigation or footer. The footer shows your church name, location, and email, links to your website, the prayer request form, and the connect card, and a "Powered by TheFaithApp" credit. The logo, name, location, email, and website come from your church settings. See [Settings, Branding, and Customization](/product/settings-branding-and-customization). ## Share the Pages Each page has its own link. The easiest way to get one is to copy the Visit or Connect link from **Visitors** in the dashboard. Every public page follows the same pattern, built from your church's public identifier: | Page | Path | | -------------- | -------------------------- | | Visit | `/{church}/visit` | | Connect | `/{church}/connect` | | Devotionals | `/{church}/devotionals` | | Campaigns | `/{church}/campaigns` | | Outreach | `/{church}/outreach` | | Give | `/give/{church}` | | Prayer Request | `/prayer-request/{church}` | `{church}` is the identifier you see in any link copied from the dashboard. Once a visitor is on one page, the header takes them to all the others. ## Place a Page Inside Your Website If you embed a page in your own site, add `?embed=1` to the end of the link. The header and footer are hidden so the page sits inside your site's own navigation. [New Visitor Journey](/product/new-visitor-journey) shows how to embed the Visit and Connect forms step by step. ## Phones The header keeps the church identity and menu button visible on phones. Tap the menu button to expand the links below it; no sideways scrolling is needed. Tap it again to close the menu. Keyboard users can also close it with Escape. ## Notes * Published forms offer a retry for temporary loading failures. A failed submission keeps entered answers while the page remains open. If receipt is uncertain, retry without changing the answers so the same submission can be checked safely. Wait for **Response received** before closing the page. * Form answers are not saved as a browser draft. Closing or reloading the page may lose unsent answers. * The header is also hidden on a signed-in member's own profile page, which has its own navigation. * Visitors of one church never see another church's pages, giving, or prayer requests.