---
tags: rangers, publication workflow
---

# Rangers Publication Processes

https://hackmd.io/@daohaus/rJvZVoTSq

- Jam with Bau and JP on 5/27/22
- Want a low lift for creating and publishing content

## Logseq as an Input

- **Would be a single step in the process**
- Taking notes in Logseq and then syncing across GitHub
- Can be an input that informs our writing and content
- Concerns with adoption:
- Needs to be frictionless as possible
- Can feed HackMDs into it
- Already have overhead, so how can we reduce it?
- Need to be intentional about how to use it
- What are the goals?

## POSSE

- Post on Site Syndicate Elsewhere
- Steps:
- 1) We'd create our own content in HackMD/markdown format
- 2) Keep versions of truth in our DAOhaus GitHub
- Canonical entry of an article
- 3) Post on our own site/blog
- We post the content on our blog
- 4) Syndicate the same content elsewhere
- Post to Mirror or other platforms, and link back to our initial blog post
- "See this article on our DAOhaus blog" -> Link to the article
- One article we write:
- On our blog, on Mirror, on Medium -> whatever platforms we choose, but there is a version on our blog and also the canonical is in our GitHub
- We have these in place except for #3 -- what would this look like?
- Look to how MetaGame displays content and how they relate to the community -> Playbooks, the Wiki, their dashboard, etc.
- https://metagame.wtf/dashboard
- Surfaces different types of content: Read, Listen, Watch
- Model similar to this
- *Read*: go to the blogposts on the site
- Where would this pull from? GitHub or a light CMS
- *Watch*: Twitch or YouTube

## Who would be involved?

- More collaborative process across all the Rangers: What would the process be?
- Managed through GitHub -- working openly and collaboratively
- As opposed to having changes managed strictly in HackMD
- Folks write locally in Markdown -> push and pull to and from GitHub
- Are we comfortable with notes being in GitHub flow as well?
- Or could this be in HackMD and then the *canonical version* be in GitHub once its ready?
- Canonical version of the article is in GitHub
- Notes that lead into this can be in HackMD
- `/blog/article-name.md` in the repo
- TW (or another person) would own the blogposts -- but having a dedicated role/person doing this and having a focus on the blog post output

## Site Overhaul (Work in Progress)

- Still fairly early in the process, but there will be
- 2 Landing Pages:
- 1) Developer focused, 2) DAO Operator (summoner, contributor, coordinator, etc.)
- Homepage:
- Captures all of these things and directs folks to other areas of the site that are relevant for them
- Top-down process for building this right now
- What are the high-level ways / language we can use to convey everything to both audiences to users?
- "Building DAOs is hard. DAOhaus makes building DAOs easy."
- Tagline + Hero
- Visual rework + spots for copywriting updates
- Good opportunity for us to leverage a blog on our site since we're reworking things anyway
- How does this integrate into the site overhaul?
- Preserve the current content on the site?

## Next Steps

- Look into the HackMD / GitHub version control sync
- Can this be finetuned to only use a certain tag?
- How does this work at the organization level?
- Incremental wins along the way and build out the content process
- Content will take time to develop anyway -- as we're creating the content we can then figure out the publishing pieces until the site is ready
- Site meeting:
- Tuesdays at 12 EST