---
title: "New Print Archetype 🖶"
date: "2023-07-13T16:03:24+03:00"
author: "anybody"
contributors: ["constantinos-miltiadis.md"] 
draft: true 
keywords:
  - archetype
  - internal
  - guide
abstract: |
  This is a copy of the archetype for creating new `print` items, including instructions for creating and properly editing `print` items, found at `root/archetypes/article.md`
  Leave `draft:true`
---

Please follow ![conventions](article:int-conventions) for file names, and instructions for ![new content creation](article:int-content). 
The Hugo terminal command for creating a new `issue` is: 
```
hugo new print/p-issue-5.md
```

This will create new file at `content/print/p-issue-5.md`.  The new file will be created according to the archetype for articles at `root/archetypes/print.md`. 
The new file will be created as a draft (`draft: true`) and will contain the instruction steps below. Please complete all required steps before publishing new content. 

# Sample YAML header 

If creating a new entry via the online preview page, the new entry will be empty. Please use the sample YAML file below as starting point, and also copy to the new file the instructions provided below.  

```
---
title: "Print Article X ⚫ 🖶"
date: "2023-07-13T16:03:24+03:00"
author: "file-creator-put-your-name-here"
draft: true 
print: "article/sample-article.md" 
---
```
# Instructions to file creator

File naming
1. If this concerns an issue, say `issue-5.md`, name this file `p-issue-5.md`. If this concerns an article say `article-title.md`, name this file `p-article-title.md`

YAML Fields
1. Put **your name** in the field `author` inside "quotation marks" as in->`author: "creators name"`
2. Set the **title** to: 
	1. Issue X Print (for issues, where X is the issue number or name)
	2. Article title Print (for articles) 
3. Set the correct **print destination** (e.g. "issue/issue-x.md" or "article/article-name.md"). ERRORS WILL BREAK THE SITE.  
4. Set the **draft flag** accordingly (false will make this public)
5. Delete this comment section. 
6. Git commit and push your changes if/when applicable, providing a commit message describing your changes. 
7. Done!

*Note: Items that are not public/published (`draft: true`), cannot have a public/published print.*
*Note: Print items should not have any content under the YAML header.*