---
title: Poster Boost UX Review
tags: ux, boosts
---

# Poster Boost UX Review

## Scope
1. UX Recommendations
2. Copywriting
3. Documentation (Boosts Catalog)

## UX Recommendations

**1. Proposal 1: Change name from `Post Markdown to IPFS` to `Publish New Document`**
> Rationale: Use more straightforward language
- Proposal Flow stays the same:
- Show a proposal form with Markdown Editor
- WHEN proposal form is submitted THEN the Markdown Document is added to Docs in DAO's metadata
- **Edits:**
- [ ] Change proposal from `Post Markdown to IPFS` to `Publish New Document`
- [ ] Change proposal description to `Create and post a Markdown document to IPFS using the Pinata API`

**2. Remove Proposal: `Post Markdown to Chain`**
> Rationale: Currently, there is no meaningful difference in use case / utility for posting something to chain vs IPFS, so let's default to posting all docs to IPFS

**3. Proposal 2: Change name from `Ratify Markdown` to `Publish & Ratify Document`**
> Rationale: We keep the "Publish Document" language constant and add a "Ratify" step to tell users that this step is (1) creating the doc and (2) making it official.

- Proposal Flow stays the same:
- Show aproposal form with Markdown Editor + Docs Location field
- WHEN proposal form is submitted
THEN the proposal goes for voting
- WHEN proposal is passed
THEN the Markdown Document is posted to IPFS
AND the Markdown Document is ratified
AND the Markdown Document is displayed at Docs Location
- **Edits**
- [ ] Change proposal name from `Ratify Markdown` to `Publish & Ratify Document`
- [ ] Change proposal description to `Create a Markdown document on IPFS and propose document for ratification by the DAO`

**4. Proposal 3: Change name from `Ratify Document` to `Ratify Existing Document`**
> Rationale: We keep the same language here, but add "Existing" so that it shows that we are NOT creating a new document, but choosing an existing document for ratification

- Proposal Flow stays the same:
- Show aproposal form with Docs selection dropdown + Docs Location field
- WHEN proposal form is submitted
THEN the proposal goes for voting
- WHEN proposal is passed
THEN the Markdown Document is posted to IPFS ratified
AND displayed at the Docs Location
- **Edits**
- [ ] Change proposal name from `Ratify Document` to `Ratify Existing Document`
- [ ] Change proposal description to `Propose an existing document for ratification by the DAO`

**5. Filters: Change filters to only "Ratified" and "All"**
> Rationale: The current IPFS/Chain filter is not meaningful in helping users filter through docs
- **Edits**:
- [ ] Remove `IPFS` and `Chain` filters

**6. Proposal 4: Create New Proposal called `Configure Document Location`**
> Rationale: This caters to the edge case where the DAO wishes to merely change a docs location

- Proposal Flow stays the same as `Ratify Existing Document`
- Show aproposal form with Docs selection dropdown + Docs Location field
- WHEN proposal form is submitted
THEN the proposal goes for voting
- WHEN proposal is passed
THEN the Markdown Document is posted to IPFS ratified
AND displayed at the Docs Location
- Edits
- [ ] Create new Proposal with name `Configure Document Location`
- [ ] Create new Proposal with description `Propose & edit where Ratified documents are shown in the DAO's page`

**7. Field Names**
> Rationale: Trying to create greater clarity here
- Edits
- [ ] Change `DAO Docs` Field Title to `Select a DAO document`
- [ ] Change `New Location` Field Title to `Select a location for DAO document `

**8. New Icon on Left Navbar**
> Rationale: It is not intuitive to click on Settings in the Marketplace to find DAO docs
- Edit: Add the following flow
- [ ] WHEN DAO installs `Publish Boost`
THEN the DAO page will show an additional icon (Document)
AND the icon will show `Docs` on mouseover

## Copywriting

**Boost Name**: `Publish Boost`
**Boost Marketplace Copy**: The Publish Boost helps your DAO create and post Markdown documents to IPFS. Once documents are published, the DAO can vote to ratify and display them in the DAO's home and vaults page.

This is useful for providing important information to people visiting the DAO's page, such as new member handbooks, process documents or treasury memos. Through the Poster contract, IPFS and the DAO's voting process, the documents are published, ratified and displayed in a decentralized and trustless way.

**Proposal 1**: Publish New Document
* Description: Create and post a Markdown document to IPFS using the Pinata API

**Proposal 2**: Publish & Ratify Document
* Description: Create a Markdown document on IPFS and propose document for ratification by the DAO

**Proposal 3**: Ratify Existing Document
* Description: Propose an existing document for ratification by the DAO

**Proposal 4**: Configure Document Location
* Description: Propose & edit where Ratified documents are shown in the DAO's page

## Documentation
:::warning
Not Started Yet
:::

### Description[#](https://daohaus.club/docs/users/boosts/boost-catalog-format#description "Direct link to heading")

Insert your description here

### Installation Steps[#](https://daohaus.club/docs/users/boosts/boost-catalog-format#installation-steps "Direct link to heading")

1. Add Proposals Playlist
2. Sign the transaction & your Boost is installed!

### Tutorials[#](https://daohaus.club/docs/users/boosts/boost-catalog-format#tutorials "Direct link to heading")

### Support[#](https://daohaus.club/docs/users/boosts/boost-catalog-format#support "Direct link to heading")

For support, please contact `Email` or go to our Discord at `Discord Link`