Loomis
The panel

Content

Starter templates, what a new account's library holds, image rules, the legal pages and in-app notices.

Five screens decide what is already there when somebody arrives, and what they are told once they are inside. None of them is about code, and all of them change what a user reads.

Templates

Content → Templates is the set of starter projects: the things a person can begin from rather than from an empty folder.

PartWhat it decides
The templatesName, description, and the files each one starts with
Plan accessWhich plans may use them
FeaturedWhich ones are shown first
OrderThe order they appear in

A good template is the difference between an empty product and a product with a point of view. Two finished templates do more for a new account than ten settings do.

Library defaults

Content → Library defaults decides what a new account's library contains on its first day: the suggested items on the shelf, and the limits that apply to it. Changing this does not change anybody's existing library, which is why it is safe to experiment with.

Image generation

Content → Image generation is the rules for pictures.

SettingWhat it does
Models offeredWhich image models are available, and which one leads
Prompt ceilingThe longest prompt allowed, in characters
Refused wordsWords the prompt may not contain, matched whole and case-insensitively

Refusals are phrase-aware: a refused word inside a longer one is not treated as a match, which is what stops a rule about one word from accidentally banning an unrelated one that contains it.

A refusal is explained rather than silent

A prompt refused here produces a sentence naming the rule, not an empty result. The list of refused words is visible on the same screen, so a person who is stopped can see why.

Content → Legal pages is every page the installation is bound by: privacy, terms, cookies, acceptable use and refunds. They already exist as routes and already render. What they render is replaced from here.

Fill in the identity fields: entity, address, contact and country. Anything left blank shows as a bracket to make the gap obvious.

Write a body per page. The pages accept a set of tokens, such as the entity name, so that one change reaches every document.

Give each page a version and an effective date, which is what makes "the terms you agreed to" a statement about a date rather than a hope.

Publish. A page with no body shows the starting point rather than an empty screen.

The shipped text is a starting point, not a policy

It was written to be plausible and to cover the shapes a policy needs. Replace it with text you are willing to stand behind in your own jurisdiction before you take money from anyone or store a single user's data. This is the paragraph in this manual that matters most.

Notices

Content → Notices is what appears inside the product: announcements, changelog entries, and anything you want everybody to read once.

FieldRule
StartRequired. A notice with no start has no way to appear
EndOptional. Without one it stays until it is removed
ContentWhat it says, and whether people can dismiss it
OrderWhich notice is shown when several are eligible

Two caps apply and both are shown: how many notices can be written, and how many may be shown at once. A person sees the newest eligible one first, and dismissing it moves the next into its place.

Removing a notice is staged until you save

The same applies to switching one off. The screen keeps your changes as a draft and shows what will change, and nothing reaches users until Save is pressed. It is the one screen in this group where that is true, and it exists because pushing a notice to everybody is not something to do by accident.

The short version

I want to changeScreen
What a new account starts fromContent → Templates
What a new account's library containsContent → Library defaults
Which models may draw, and what they may notContent → Image generation
The privacy policy and the termsContent → Legal pages
An announcement inside the productContent → Notices