Content and forms

Hosted content

A list on a page, such as team members, prices or a menu, can move from the site's code into hosted content. Then anyone in your organization, editors included, changes it in the app's Content tab without opening the editor.

To move a list, open the editor's Content tab, pick the list and press Move to hosted content…. Designers, developers and owners can do this, for lists written in the file that shows them.

In the app's Content tab, pick the site and the collection, then change fields, add records, reorder them or delete them. Changes save when you leave a field.

A live site reads its content when it is built. After changing content, press Publish content changes: Frontage rebuilds the live site with the new content, which takes a minute or two. Until then the live site shows the content as it was.

Limits on the Free plan: 3 hosted collections per site, and 100 records per collection.

Form messages

Contact and sign-up forms on a site published by Frontage send their messages to Frontage. Every message is kept and listed under Form messages on the site's page, newest first, with a Download CSV button.

Each message is also emailed to your organization's first owner. During the beta, these emails are limited to 60 a day across all of Frontage; a message over that limit is still kept in the app.

Pages on other websites cannot send messages to your forms from a browser. Each form takes at most 30 messages a minute from one visitor, and up to 32 KB per message. A hidden field that people never see catches automated spam that fills in every field.