Write static pages

Every site needs an About page, a way to get in touch and its policies. Arc CMS gives you these as standard pages that admins edit in the editor. For text that never changes you can also write hand-made HTML pages, served at /p/{name}.

The standard pages

The setup wizard creates a content type called Info Pages, at /info, with six drafts: About, Contact, Frequently asked questions, Privacy Policy, Terms and Cookie Policy. Each is an ordinary entry, so you get the editor, drafts, version history, SEO fields, the sitemap, search and translations.

1. Open Content, then Info Pages. On an install from before the standard pages, open Content types and choose Add standard pages first; it adds only what is missing.

2. Open each page and replace every prompt that starts with [Replace:. The policies start from an outline of the usual sections, filled with your name, email and address from Settings, About where it can. They are not legal advice: have them checked for where you work.

3. Fill in Settings, About: the contact email, public phone, address and social links. The Contact page prints them, so they are typed once.

4. Publish the pages you want. The editor asks before publishing a page that still has a [Replace: prompt. Delete a page you do not need, or leave it unpublished.

5. To change their order in the footer, choose Arrange on the Info Pages list and drag them into place.

Each page turns on what it needs with five fields:

The Contact page

The Contact page has a layout of its own, chosen with Layout: Contact in the editor's Basic tab. It is laid out in three rows:

1. The title and your text, full width.
2. Each place under Locations: the map on the left, the place's name, address and a directions link on the right. Add your office there; the map comes from the address you pick.
3. On the left, boxes for your email and phone from Settings, About, your social links, and your Info boxes. On the right, the contact form.

Rows and boxes with nothing to show are left out, and on a phone everything stacks. A Contact page created before the layout existed keeps the standard look until you pick Layout: Contact; on such an install, choose Add standard pages on Content types first to add the Info boxes field. To change the layout itself, put your own src/custom/site/templates/info/detail-contact.html in place (see Layouts).

Once published, the pages are linked for you:

• The default footer lists every published standard page, in their arranged order and in the page's language, above a copyright line with the year and your site name. Your own footer can do the same with data-arc-site-loop="pages" (see Design templates).
• The terms notice on every signup form links "Terms of Service" to /info/terms and "Privacy Policy" to /info/privacy-policy, and the contact form's privacy line links to the privacy page.
• The cookie banner links to /info/cookie-policy, unless you set its link yourself in Settings, Site Usage.

Publishing or unpublishing a standard page, changing its title or arranging them republishes the whole site, so every footer lists the same pages. The pages use the info template folder; restyle them with the .arc-page classes in your src/custom/site/site.css, or replace the template with src/custom/site/templates/info/detail.html.

Hand-written pages

A hand-written page is an HTML file in src/custom/site/pages/, served at /p/{name}. Arc CMS ships two examples, a privacy policy and a cookie policy, in public/_site/pages/. Use one for text that rarely changes and needs no editor; anything editors update belongs in the standard pages or another content type.

1. Copy public/_site/pages/privacy-policy.html to src/custom/site/pages/, or start a new file there. A file with the same name as an example replaces it at the same address.

2. Replace the <title>, the <meta name="description"> and the body text with yours. Keep the page a whole HTML document.

3. Keep <arc-header></arc-header> at the top of <body> and <arc-footer></arc-footer> at the end: they become the site header and footer. Use the site's classes (Bootstrap is loaded) rather than your own stylesheet. data-arc-site prints your contact details here too, and a signup or contact form works.

4. Check it locally: with npm run dev running, open /p/privacy-policy.

5. Deploy the website with npm run deploy, choosing Website or Everything (see Deploy). After the deploy it publishes the pages with your header, footer, styles and search box filled in, and lists them in the sitemap.

Link to a hand-written page as /p/{name}. On the live site that address redirects to the published page at /pages/{name}; in npm run dev only /p/{name} exists. Republish website (Content, Content types) also rebuilds every one, for example after you change the header.

The terms notice and the cookie banner prefer the published standard pages. Without one, the notice links to your own src/custom/site/pages/terms.html and privacy-policy.html when you have them, and otherwise shows the words as plain text; Arc CMS's sample policy is never linked. The cookie banner shows only on pages the app draws, such as sign-in, the form pages and search, not on published pages.

Next

Give the sign-in page your brand: Brand the sign-in page. The full reference for content, including the standard and static pages, is Content.