settings.json and pages/.
Run CLI commands from this folder so they use the right publication.
Setup also generates
package-lock.json when npm installs dependencies. Commit
the manifest and lockfile to keep the CLI version consistent after cloning.
The homepage is generated from your articles. You do not need a
pages/index.mdx file; the renderer excludes index.md and index.mdx from
article pages. See Homepage to change the heading and feed.
Assets
The default CLI setup includes local images and fonts. The optional--remote-assets setup uses hosted
URLs and omits public/. Sites created through Lettercamp Cloud use remote assets.
For standalone sites, put files in public/: public/images/cover.jpg is available
at /images/cover.jpg. Local preview serves these files, and static builds copy
them into the output. The assets/ source folder is not a public file server.
lettercamp deploy uploads
referenced local JPEG, PNG, WebP, and GIF images and substitutes hosted URLs in
the deployment copy. Your local files keep their original paths. It does not
deploy the public/ directory as static files.
Before deploying a starter created with local assets to Cloud, set design.typography.localFonts to
false so its fonts load from the CDN. Custom fonts and other media need hosted
URLs. See Typography and
Cloud publishing for details.
For the full list of source folders included in a deployment, see
Files included in a deployment.