- either *via the terminal*, which requires a local working clone of the repository, and will instantiate a new file according to archetypes (see [via the terminal](#cli)), or
- *online via the Sandpoints preview page*, which only requires repository access, and will create *new empty files* (see [via online preview page](#online)).
*Note: both workflows require write access to the project repository.*
# Title emojis {#emojis}
It is recommended to use emojis[^emj] in the title of any new or in progress entries so as to keep track of new and WIP items as well as potential mistakes.
Each new item created via the archetypes (via the terminal) will feature two emojis: one to signal a draft (⚫) and a second one associated its particular content type (e.g. 📕📑🧜♕🖶☮).
The table below describes the logic of emojis used.
If created via the terminal, each newly created item:
- is created after its corresponding archetype (found in `root/archetypes/`);
- is set to draft (`draft: true`), meaning that it's not public/published;
- includes a list of required steps for preparing the entry for publication (copied in the articles of this issue);
- will have two emojis in its title (see [title emojis](#emojis)).
*Note: this workflow requires a local clone of the repository as well as a Hugo installation, in addition to repository credentials.*
# New content via the online Sandpoints preview page {#online}
The project preview page allows for both creating new entries and also editing existing entries. To access the preview page append `/_preview/` to the root (sitemap) URL.
*Note: Creating new items does not make use of archetypes. Any new item created with this workflow will be created empty, and will require a YAML header to work.*
## Preview site interface
The preview site features a toolbar with five options (Screenshot 1), explained in the table below.
Note that adding a new item will create a new empty Markdown document, which is also missing the required YAML header (Screenshot 3).
For creating new items it is strongly recommended to start with a copy of archetype corresponding to the specific type of item you are creating, found in the 'archetype' contents of this issue. These include the required instructions to follow as well as sample YAML headers to start with.
