--- title: "{{ replace .Name "-" " " | title }} ⚫ 📕" date: "{{.Date}}" author: "file-creator-put-your-name-here" draft: true has_articles: ["article-test.md"] editors: ["jane-editor.md", "joe-editor.md"] keywords: - draft abstract: | The text of your abstract. (Below is an instruction checklist for issue-file creators/editors) --- # Instructions for issue-file creator/editor: 0. [x]  Put a checkmark to all items of this list that have been completed by changing: > `1. [ ]` to `1. [x]` 1. [ ] **File naming**: Follow ![conventions for issue file-naming](article:int-conventions). Example: > `issue-5.md` 2. (File editor) **Insert your name** in the `author` field inside "quotation marks" as in: > `author: "creators-name"` 3. [ ] Set the `title` to the **title of the issue**, as in: > `title: "Issue 5: What is Game Design Research?"` 4. [ ] Create **entries for issue editors** – if they are not there – and add their bio/info. 5. Add **issue editors** as above (comma separated; inside quotation marks; including extension): > `editors: ["jane-editor.md", "joe-editor.md"]` 6. [ ] Add **issue keywords** -- if applicable. Follow exact formatting as above, otherwise the site will break. ``` keywords: - keyword one - keyword two ``` 7. [ ] Fill the **issue abstract** -- if applicable. Following precise formatting, otherwise the site will break. 8. [ ] **Add the articles included in the issue** as above (comma separated; inside quotation marks; including extension): > `has_articles: ["article-test.md", "article-2.md", "article-3.md"]` 9. [ ] **Parent issue to journal** - If, and only if this issue is ready to be published and `draft: False` you can parent go to `content/journal/jgdr.md` and add the name of this file (not title) to the field `has_issues`. Note: articles included in this issue will not appear unless this is parented to the journal item. Example: > `has_issues: ["this-issues-file-name.md"]` 10. [ ] **Add issue-editorial text** below this section. 11. [ ] **Log potential problems or pending tasks** with this issue by making another check-list below (commented sample lists provided below). 12. [ ] **Git commit and push if/when applicable**, providing a commit message describing your changes. 13. [ ] **Set the draft flag** accordingly. *False will make this public*: only do that when ready to publish, and when there is already a 'print' file for the issue. Leave `draft: true` when in-progress. 14. [ ] Feel free to put this block inside comments, to be able to view the actual content properly. 15. [ ] Delete this section when all is in order. 16. Done!