---
# System prepended metadata

title: Procedure for Writing Lore Documents
tags: [Work-In-Progress, Revision-In-Progress, Finalized, Awaiting Approval]

---

# Procedure for Writing Lore Documents

Hello Team!

As of our meeting on the 26th of May, 2023, the lore team will have a new procedure for the drafting, approval and release of documentation relating to the factions, setting and more of the Shiptest universe. Please consult the information below for more details.

## How To Get Your Document Formalized: A Four-Step Process

### Step One: Write Your Document
Got a cool idea for a new planet, faction, company, etc.?  Write it out! Put your draft (however complete) onto the team-only HackMD, and make sure to tag it with the 'Work-In-Progress' tag. If you have questions about how a piece of lore may interface with something someone else has written, consult the loreowners document (soon to be written by Ashturi) and ask them! When you're ready to present your first draft, move on to Step Two.

### Step Two: Present It To The Team
Once your first draft is complete, now it's time to talk to the team! Mark your first draft with the 'Awaiting Approval' tag instead of the 'Work-In-Progress' tag. Give the lore head and maybe a couple other interested curators a ping and ask them to read over your document and provide feedback. This feedback should take the form of both editorial advice – grammatical errors or word choice, for example – as well as thematic advice, such as if the lore clashes with existing themes or with other pieces of existing lore. Once you have all your feedback from the first pass, move on to Step Three.

### Step Three: Revisions
Take the feedback you received, and see what you want to do with it. While a lot of feedback is subjective, bear in mind that deciding not to follow feedback from lore administrators might impact your lore's acceptance into canon if you can't properly justify your decision (and if you can, great!). In this stage, you should mark your second draft with the 'Revision-In-Progress' tag. Once you've followed this first set of feedback in whatever form you see fit, submit it to the team again. If you receive more feedback, continue revising. If the team is satisfied with your work, move on to Step Four.

### Step Four: Publication!
Your lore is ready to see the light of day! Remove the 'Awaiting Approval' and 'Revision-In-Progress' tags and add the 'Finalized' tag. Make sure it's visible to the general public, and bask in the glory of your addition to the canon.

## Conclusion
And that's it! I hope this document has provided you with the tools necessary to make your lore documents the best they can be. Good luck out there!

###### tags: `Finalized` `Work-In-Progress` `Awaiting Approval` `Revision-In-Progress`