diff --git a/config/_default/params.yaml b/config/_default/params.yaml
index f48d499..ed7db4a 100644
--- a/config/_default/params.yaml
+++ b/config/_default/params.yaml
@@ -3,3 +3,4 @@ github:
 mastodon: 
   url: https://mastodon.lescommuns.org/@opentermsarchive
   username: "@opentermsarchive@mastodon.lescommuns.org"
+email: contact@opentermsarchive.org
diff --git a/content/memos/writing-reference.en.md b/content/memos/copywriting-reference.en.md
similarity index 97%
rename from content/memos/writing-reference.en.md
rename to content/memos/copywriting-reference.en.md
index f33649c..5c6999c 100644
--- a/content/memos/writing-reference.en.md
+++ b/content/memos/copywriting-reference.en.md
@@ -1,8 +1,8 @@
 ---
-title: "Writing reference"
+title: "Copywriting reference"
 ---
 
-# Writing reference
+# Copywriting reference
 
 Each memo must be composed of the elements detailed below. You must follow this structure when writing your memos.
 
@@ -78,7 +78,7 @@ Each memo must be composed of the elements detailed below. You must follow this
 >
 > OpenAI Ireland Ltd is a Dublin-based subsidiary of OpenAI [set up](https://openai.com/blog/introducing-openai-dublin) in 2023.
 
-## Full examples
+## Complete examples
 
 ### Memo 1
 
@@ -107,7 +107,7 @@ Each memo must be composed of the elements detailed below. You must follow this
 
 > **Meta expands reach against child exploitation**
 >
-> _Facebook · Community Guidelines · June 13, 2022_
+> _Facebook ▪ Community Guidelines ▪ June 13, 2022_
 >
 > The section on child exploitation for both Facebook and Instagram [expanded](https://github.com/OpenTermsArchive/france-elections-versions/commit/0396436542fa7ef8dd8ae4dd02ff0ed5500e08a2) to cover not only publications that exploit minors, but also “any activity” related to such acts.
 >
diff --git a/content/memos/how-to-publish.en.md b/content/memos/how-to-publish.en.md
new file mode 100644
index 0000000..39bf68a
--- /dev/null
+++ b/content/memos/how-to-publish.en.md
@@ -0,0 +1,27 @@
+---
+title: "How to publish a memo"
+---
+
+# How to publish a memo
+
+This guide will help you publish a memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/).
+
+No technical skills are required.
+
+## Prerequisites
+
+- A drafted memo compliant with the [copywriting reference]({{< relref "/memos/copywriting-reference" >}}).
+
+## 1. Send
+
+Send your memo to [{{< param email >}}](mailto:{{< param email >}}?subject=Publish%20a%20memo&body=Dear%20Core%20team%2C%0A%0AI%20would%20like%20to%20publish%20the%20memo%20below.%0A%0AIt%20is%20based%20on%20my%20original%20work%2C%20and%20I%20have%20reviewed%20the%20reference%20at%20docs.opentermsarchive.org%2Fmemos%2Fwriting-reference%2F%20and%20I%20have%20made%20sure%20the%20content%20complies%20with%20it%20before%20sending%20this%20text%20to%20you.%0A%0AI%20understand%20that%20it%20might%20take%20up%20to%20two%20weeks%20for%20this%20text%20to%20be%20reviewed.%0A%0AHave%20a%20good%20day%21) by writing it in the body of the email or as a file attachment. Feel free to add any comments or questions you may have about the content or format.
+
+## 2. Review
+
+The Open Terms Archive core team will review your memo as quickly as possible.
+
+If necessary, we will suggest changes and discuss them with you. Note that review times may vary depending on the number of changes required, the speed of exchanges, and the availability of reviewers. If you do not hear from us within two weeks, please do not hesitate to contact us again by the means of your choice.
+
+## 3. Promote
+
+Once the core team has published your memo on [opentermsarchive.org/en/memos](https://opentermsarchive.org/en/memos/), we will inform you and provide you with the URL address of your memo. You should then promote it through the media and to the people you consider appropriate. Whenever possible, please associate the hashtag `#TermsSpotting` with your memo promotion, in order to provide visibility to the overall Open Terms Archive project and analysis.