Model the content before adding the entries
A collection is a repeatable content structure, not simply a folder with a nicer name. Decide which values are shared across records, which are optional and which values the published design actually needs. Articles, projects and team members are common examples. A one-off page with its own layout may be better maintained as a page.
Start with the CMS setup guide, then build the portfolio example if you want to see a schema connected to cards and detail pages. The Harbor Studio examples are illustrative. Their job is to make the editing decisions concrete, not to imply a client outcome.
Know where the data and layout live
Webyaam stores CMS entries as Markdown files under src/content, with collection definitions in the visual composition and a generated Astro schema and detail route. A collection list displays several records on a page. The detail layout displays one record at its own URL. Creating a field gives you structured data; a particular card or custom component must use that field if it should appear in that part of the design.
Choose field types for the editor's actual job. A controlled option list can keep categories consistent. A number should represent numeric data rather than an identifier with leading zeroes. Required values should be genuinely necessary for published content. A present boolean value of false or number value of zero is different from a missing value.
Keep editorial status separate from a release
Input changes, saved source, the entry's draft flag and the site's released build are different checkpoints. Draft entries are excluded from Webyaam's generated published lists and detail routes, but an authorized collaborator can still read the source. A draft flag is not a private document vault.
After approving an entry, save the source and build or publish the intended new snapshot. Conversely, turning an entry back into a draft does not remove a page from an old static snapshot until the updated release is served. The publication guide includes a checklist for both directions.
Design a workflow another person can operate
Have the intended editor create a draft, fill the required fields, save, reload and review a detail page. Include a correction and a missing-value example in training. Explain which collection values appear on cards and which affect a detail page. Document image expectations and the difference between changing a label and changing a public route.
Keep URLs stable when possible. When a public route or slug must change, plan a suitable redirect or missing-page response on the hosting layer. A schema setting is not a general redirect or scheduling service. Future dates are data unless a separate publication process implements scheduled releases.
Decide what happens outside the platform
Markdown content can travel with an Astro source export. That does not install the Webyaam account system and editing dashboard on another host. Agree on who will edit the source, trigger builds and maintain form or analytics services after an independent deployment. File-based collections are useful for content sites; they should not be treated as an unplanned replacement for transactional application data.
Use the guides below as a maintenance path: set up the model, connect the presentation, practice publication and prepare the handoff. Check current plan capacity against your expected number of entries before committing to a large content library.