Newsletter

Task management & content backup for ALife Newsletter

• [2022-07-22] Awarded the ISAL Exceptional Service Award at ALIFE2022

Issues

• August 2020
• October 2021
• December 2021
• April 2022
• June 2022

---

Issues published on GitHub Pages: https://alife-newsletter.github.io/Newsletter/

Subscription/Contribution

You can subscribe here.

Contribute to any section of the next newsletter here!

---

for Repository Contributors

TODO

• Improve the CSS of the automated generated newsletter
• Add the old newsletters here
• Automatically generate index.html
  • Or maybe not? Need a way to hide "in progress" editions
• Add permalink to each contribution
• Twitter bot to remind people to contribute / talk about past contributions?

Branches

• main
  • The main branch we commit to.
• gh-pages
  • A branch for GitHub Pages. Only CI modify it. Do not manually commit to it.

How to Publish Newsletter

1. update subscibers

• download new subscribers from google form as csv
• log into mailjet
• update contact list in contact menu in mailjet (use csv) (do not "resubscribe")

2. create newsletter

• go to "marketing templates"
• duplicate last newsletter
• update subject and sender (check that sender is gmail, not proton)
• update html
• "save and publish to gallery" <= DO NOT FORGET this step

3. send

• create a campaign from the next page
• schedule or send now

How to Use Scripts

Basically those scripts are self-explanatory, so $ <script> -h shows what arguments it accepts.

# makeNewsletter.py
# generates a static html for the specified edition newsletter
$ python makeNewsletter.py <edition_directory_name>

# makeNewEditionDirectories.py
# creates files and directories for a new newsletter issue
$ python makeNewEditionDirectories.py <new_edition_number>

# makeAllEditions.py
# CI uses this script
# generates static html files for all editions
$ python makeAllEditions.py

How CI Works

Generates static html files and publishes them to GitHub Pages

It works on GitHub Action and the workflow file is .github/workflows/gh_pages_deploy.yml

The action is triggered by pushing the main branch, and it generates all editions' static html files and publish them on GitHub Pages.