As a way to start generating discussion, we created some mockups of what the new Project content on the site could look like. Below are two mockups for a new main Projects page and an example of a page about one specific Project.
| Table of Contents |
|---|
Proposed
...
Projects Page - Replacement
- This gives priority placement to the 6 graduated a small number of featured projects and gives secondary placement to the incubation projects. This other projects. Featured projects are graduated projects with active communities that the Marketing lead thinks we should highlight. Hyperledger's Marketing lead looked at the analytics on the site and people don't spend long on any one page so we need to make the information as easy to digest as possible. So this design intentionally limits the information we're providing to prevent people from feeling overwhelmed at trying to process details about all of the projects at once. Priority placement is also an incentive for incubation projects to graduate.
- Note that combining Indy and Aries into one description was an attempt to limit the number of descriptions on the page but it might be more confusing this way. Another option is to list just Aries as a featured project and then Indy would be clearly related to Aries on the Aries page.
- This has a richer project description than the current site – descriptions show without needing to click on a logo, there is space for tags and a Resources drop down for direct access to project links.
- This has a link to a Getting Started guide which would be a new page that helps people navigate to the projects that meet their needs.
Proposed Getting Started Page - New
The goal of this page is to present a lot of detailed information about projects to help people find the one that is right for specific Projects:them – for example, I want a project that supports a specific token type and a specific form of consensus.
Proposed Project-Specific Pages - Replacement
- This has a section that sorts links by different personas (Developers, Users, Business Analysts) to make it easier for people to find what is relevant for them
- This has a new 'Related Projects & Labs' sidebar that can link to the other projects that work with this project – currently the Landscape and Project pages don't create any connections with projects that are related. Related Labs aren't listed here, but I think it would make sense to put them below the projects in the sidebar and listed in a secondary way – perhaps just a text link to the relevant labs.The marketing recommendation is to list no more than 3 related projects. For projects with more related projects we can add a link to the Getting Started guide which would have a full listing of all compatible projects. The proposed project relationships to include are below.
| Project | Related Projects |
|---|---|
| Aries | Indy, Ursa |
| Besu | Bevel, Cactus, Caliper, Firefly |
| Bevel | Besu, Fabric, Indy |
| Cactus | Besu, Fabric, Iroha |
| Caliper | Besu, Fabric |
| Cello | Fabric |
| Fabric | Bevel, Cactus, Caliper, Firefly |
| Firefly | Besu, Fabric |
| Grid | Sawtooth |
| Indy | Aries, Ursa, Bevel |
| Iroha | Cactus, Ursa |
| Sawtooth | Transact, Grid |
| Transact | Sawtooth |
| Ursa | Aries, Indy, Iroha |
- This has a section for tags if we want to use those for projects
Proposed new Getting Started page:
The goal of this page is to present a lot of detailed information about projects to help people find the one that is right for them – for example, I want a project that supports a specific token type and a specific form of consensus. A challenge here is how to provide a lot of details around multiple projects in a way that is consumable, so filtering is a big part of the interface.
...
- We should probably remove the Upcoming Events section since we don't have an easy ability to keep that content current for all project pages.
