• Determine and document best practices for Notion permissions.

• Advise and support guilds on the implementation of best practices.

• Review ongoing permissions and flag potential risks.

• Review pages within the global workspace and deal with any orphaned pages.

• Deal with any intrusions as they arrive.

• Back up the Notion site regularly.

We have a

Default Page Layout [TEMPLATE 🚧]

available for all contributors to use.

1. Reduce the cost of communication, task switching, and superfluous redundant work.
Consistency in how knowledge is organized makes it easy to find what you need. It also makes it easy to add/update information because there’s context and predictable/repeatable structure.

2. Increase our effectiveness when working asynchronously (async).

3. Be maximally respectful of each others’ time when working together.
Tracking action items and deliverables async creates a starting agenda for each meeting that picks up right where you left off.

• Create a single “source-of-truth” where all updates from autonomous WGs and contributors can be easily compiled to slay that pesky Moloch.

• Define “top-level” articles owned by Workgroups, Core Contributors, and
All pages must be owned by a Workgroup or Project Workstream

• Multiple people can collaborate on docs if we have appropriate Role-Permission mapping

• Teach Workgroup Leads & Project Champions about these

• Rollout a Notion Administrator role to all guilds

• Move as many members to guests as possible

• Backup the Notion data regularly

1. Keep Occam’s Razor handy. The simplest option is the best option.
Don’t copy/paste information to multiple pages. Always link between pages.
Communicating with fewer words is harder but better than being verbose/rambling.
What's the difference between "Link to a page" and "Mention a page"?

2. Don’t delete things, especially databases since they might be linked to other databases or revived in the future. Instead, create a “Toggle List” or “Toggle Heading” toward the bottom of the page and label it “Archive”.
Archive deprecated content on the same page. Don’t move things to other pages to archive them. Moving docs alters the context under which it will be interpreted. We don’t need more docs explaining why archived files are moved.

3. Label pages under construction with [DRAFT] (at the end of the title).

4. If it can be a database then it should.
🧼
Notion Databases: Best Practices

5. Pages should not be self-referencing.
You can create recursive loops between 2+ pages.

• TODO: Standardize
  

  Contributor Database (update yourself!)
  to skill tracking database used by Ops, who will add
  🥾

  Skill Descriptions (list)
  to the contributor database
Suggestion: use a multi-select and create another page to define what the skills mean

• 📼 VIDEO: Notion Tips for Beginners (9min)

• 📼 VIDEO: Notion Tips for Productivity (12min)

• Resources from the #1 Notion Consultant

• Notion data analytics
Notionalytics
Convert Notion docs to website & link to Google Analytics

Main Bankless DAO Admin Page:

📖

Notion Administration