---
title: notaryproject.dev Information Architecture Proposal
date: 2021-08-29
tags: Notary Project, Information Architecture, TUF, Notary, Notation, CNCF, website
---

Github issue: [Information Architecture Proposal #23](https://github.com/notaryproject/notaryproject.dev/issues/23)

**Site structure**
(_note_: not all of these will be pages, some may be sections)

- [x] Landing page (`/`)
On this page we will need to include the following information:
- [ ] Organizations that are contributing to the project
- [ ] The problem the project is trying to solve and the vision for the project
- [ ] The differentiators for the project (answering the question: "Why one more signing solution?"")
- [ ] Where Notary can be used? How it works?
- [ ] News and events?
- [ ] Community (`/community`)
- [ ] Governance
- [ ] Community (details)
- [ ] meeting notes (`/community/meeting-notes`)
- [ ] Contributing/How to get involved https://github.com/notaryproject/notaryproject.dev/issues/29
- [ ] Where to start
- [ ] How we work
- [ ] Filing and working on issues for the project
- [ ] Where the community is (contacts, meetings, Slack)
- [ ] Contributing to docs (links to the doc project)
- [ ] Where to ask for more help contributing (Slack)
- [ ] Next steps
- [ ] How it works? Scenarios
- [ ] In this section we should explain the scenarios that Notary Project enables
- [x] Blog (Get the word out about the project and how it's progressing) (`/blog`)
- [ ] Docs (`/docs`)
We should have a separate document for the documentation information architecture.
- [ ] Notation (`/docs/notation`)
- [ ] v0.7.0-alpha.1 (`/docs/notation/v0.7.0-alpha.1`)
- [ ] Notation-go (`/docs/notation-go/v0.0.0`)
- [ ] TUF (`/docs/tuf/v0.0.0`)

**Top nav**

- [ ] Overview (this is link to the home page/landing page)
- [x] Community
- [ ] How it works?
- [ ] Docs - internal link to `/docs`
- [ ] [Specifications](https://github.com/notaryproject/notaryproject) initially (we don't need that in the main nav - we can include in the documentation)
- [x] Blog
- [ ] [Roadmap](https://github.com/notaryproject/roadmap) (maybe just put it on the page?) We don't need that. This is tracked in the GH project
- [ ] Notary Historic Docs - [link to github](https://github.com/notaryproject/notary/tree/master/docs). Do we need those? We can have a separate folder in the documentation to have V1 docs. We should add to the docs information architecture.

## Notes (not sure what those are for)
Docs
- Specs
notary v2 specs
tuf - ref implementation for supporting TUF
- Implementations
- notation docs
- notation-go-lib docs
- notaryproject.dev website
- meeting-notes - merge the content into the notaryproject.dev repo, shown on the https://notaryproject.dev/community/

Notary v2 Content
- **notaryproject** - Notary v2 specs - links directly to the repo not duplicated into the notaryproject.dev site
- **notation** - cli
- **notation-go-lib** - libraries
- **tuf** - ref implementation of TUF for notation (notary v2)

- Notary v1 can be refered as historic