Choose a site

After signing in, pick the site you want to work on from the sites list. Everything you see afterwards (pages, posts, media, redirects, settings, trash) belongs to that site. To add a site, a domain administrator submits a site request and a platform administrator approves or declines it. Platform administrators can also create sites directly.

Create and build a page

1. Create a new page and give it a title. The URL slug is generated from the title, and you can edit it. Slugs are lowercase letters, numbers and hyphens.
2. Optionally set a meta title and meta description, which are what search engines and shared links show.
3. Pick a layout.
4. Add sections. Each section type offers its own fields. You can insert a section at a specific position, reorder sections, hide them, or remove several at once.
5. Fill in each section. Body text supports markdown, with a formatting toolbar that includes a Video button and help for the placeholder tokens available (for example, the site name). Things to know about sections:

• A section only appears where you add one. The contact form, for example, shows only on pages that include a Contact section.
• If you switch to a layout that has no area for a section (say, a sidebar section on a one-column layout), the section moves to the main area. It is not deleted, and switching back restores its original placement.
• In a feature grid, each card's icon is chosen from a fixed list. A card with no icon is fine. New icons can't be added from the admin; they need a developer.

Publish, schedule or withdraw

• Publish makes the page live now.
• Schedule by choosing a future date and time. The page goes live by itself at that moment, with no extra step.
• Unschedule cancels a scheduled publish and returns the item to draft.
• Withdraw takes a live page down. Visitors then get a 404. Withdrawing is recorded as different from "never published." Publishing again brings the page back.

The same actions work for posts.

Preview before publishing

Use Preview to see a page or post through the real public template, with the site's own navigation and theme.

• It works for drafts, scheduled and withdrawn items, none of which have a public address.
• A banner tells you the item's state.
• Search engines are told not to index previews.
• Links inside a preview go to the live site, not to other drafts.

Write a blog post

Posts are available only on sites with the blog turned on; otherwise creating one is refused.

1. Create a post with a title (slug is generated, editable).
2. Write the excerpt and body, and add a featured image from the media library.
3. Add tags by typing names. Tags are per site, and "NetSuite" and "netsuite" count as the same tag. Existing tag names are offered as you type.
4. The byline defaults to you. You can change it to anyone who has authored on the site or has been granted access to it.
5. Publish or schedule as above.

If you make a meaningful change to an already-published post, mark it as revised so the post carries a revision date. Ordinary saves don't change a post's dates.

Pages and posts share one address space on a site (/about, /my-post), so a post can't use the slug of an existing page, or the reverse. You'll be told if you try.

Share a post to LinkedIn

On a post, open the share panel to see exactly what LinkedIn would receive, then share. You can write your own commentary (up to 3,000 characters). Otherwise it's derived from the excerpt. Sharing can't be repeated and can't be recalled, so check the preview first.

A platform administrator connects LinkedIn once from the admin. The connection lasts about 60 days and cannot renew itself, so someone must reconnect roughly every two months. Posts that have been shared carry a "Discuss on LinkedIn" link. The site has no on-site comments, so that link is where discussion happens.

Use AI assistance

In the editors, AI actions propose text based on what you've written.

• Nothing is saved until you accept a suggestion.
• You need some text for the action to work on.
• If a suggestion was cut short, you're told.
• Read-only users can't use it. If AI isn't configured for the app, you'll see a message saying so.

Manage images and files

The media library is per site.

• Upload JPEG, PNG, WebP or GIF images, or PDFs, up to 12 MB each. If a file is too large for the server, you'll see a message about the limit.
• SVG files are not accepted, for security reasons. Use PNG for logos.
• Uploading the same file twice returns the existing item instead of making a copy.
• Add alt text and a title to each item, and search by file name, title or alt text.
• Images get smaller web-ready versions automatically on upload.
• Check usage to see where an item is used.
• A file that's still in use can't be deleted. You're shown what is using it. For PDFs, "use" means a link inside page or post text. Image pickers (such as a post's featured image) offer images only.

Go back to an earlier version

Open a page's or post's history to see earlier versions, read one, and restore it. The version you replace is saved first, so a restore can itself be undone.

Delete and recover

Deleting sends a page or post to the trash; it doesn't destroy it. The response tells you what the deletion costs:

• The public address starts returning a 404 immediately.
• If the page was the site's front page, the site falls back to its post listing, or to a 404 if there is none.
• A LinkedIn share of a deleted post still points at the old address.

Restore from the trash and the item returns with its sections or revisions intact.

Keep old addresses working with redirects

When you change the slug of something that has been published, you're prompted to create a redirect from the old address to the new one. It isn't created automatically, because only you know whether the old address mattered.

You can also manage redirects directly:

• List, create, edit and delete them.
• Choose permanent (301) or temporary (302).
• The destination can be a path on the site or a full http(s) address on another site. A bare hostname is refused.
• Rules that would loop or point at themselves are refused.
• Redirects whose destination doesn't resolve to published content are flagged.
• Visitors' query strings (such as campaign tags) are carried through.

Live pages and posts always win over a redirect. A redirect is only used where the visitor would otherwise get a 404, with one exception: a redirect can retire the /blog listing address.

Configure the site

Under site settings you can edit:

• Basics: site name, tagline, contact email, whether the site has a blog, and posts per page. Turning the blog off tells you how many published posts will stop being reachable.
• Navigation: the header menu. Indent a link to make it a drop-down item under the link above it. There's one level of nesting, the first item can't be indented, and outdenting a parent takes its children with it. There is a limit on the number of items. If a save is rejected, an error appears beside the save control.
• Footer: the copyright line and footer links.
• Theme: the site's colours and typeface. Anything you don't set uses the platform default. The Accent colour also controls link colour in body text.
• Google tags: analytics and advertising IDs, per site. Mistyped IDs are refused at entry.

Control who can edit

Access is granted per site. A domain administrator can add or remove people on their sites, and each person gets either edit or read-only access. Read-only users can look but not change anything, including using AI assistance.

Administrator-only tasks

• Section types: administrators with delegation rights can rename section types, edit their help text and fields, retire them (they stay on pages that already use them but can't be added again), preview templates, and create new types. A type's key can't be changed once created.
• Migration requests: platform administrators review and approve or decline the sign-up requests submitted through a site's sign-up page.
• LinkedIn connection: platform administrators connect and disconnect it.