Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

Proposed new Project page:

  • This gives priority placement to the 6 graduated projects and gives secondary placement to the incubation projects.  This intentionally limits the information we're providing to prevent people from feeling overwhelmed at trying to process details about all projects at once.  Priority placement is also an incentive for incubation projects to graduate.
  • 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 page for specific Projects:

  • 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.
  • 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.

  • No labels