/designers-project-anthology

service/product/project overviews - made by designers for designers

Primary LanguageJavaScriptMIT LicenseMIT

An index of service/product overviews

Pages, primarily for a design audience, to:

  • introduce the service/product/project
  • it's history / current phase
  • link to the prototype(s) - behind accounts
  • link to other sources of useful information - behind accounts

This app just contains a list of service/products/projects

Each item listed has it's own app/repo

User need

As a designer joining the project/service team I need to get up to speed with:

  • context - why are we doing what we are doing now
  • where is all the stuff i need to be immediately productive
  • all the other stuff i may need, a bit less urgently than right now

Principles of this app and linked apps

  • be public by default, only protect information when necessary (marking when information is behind an account, who is allowed, and how to get access)
  • provide a means of contact

Content

Content to include (to this or linked apps)

  • background to the service/product/project - perspective a designer needs
  • how to contact people (but not names, email addresses, or any other personal information)

Content to link to (to this or linked apps)

  • screenshots (in gallery.io)
  • prototypes (do not include username/passwords)
  • user research / needs
  • other useful project/team information - to enable a designer to be productive on day 1
  • contact details - for these apps or the teams
  • you can link to information behind an organisational account

Content to NOT publish in the open

  • peoples names and other personal information
  • usernames and passwords
  • gov or organisational branding
  • anything 'political', or contentious - think would I be prepared to say this openly on the internet

To Do

  • come up with a better name / description of what these things are
  • consider the order of the list - do we need multiple lists
  • consider the status(s) of each thing in the list
  • consider other user needs - for example we believe this content to be useful outside of the design community
  • consider having one app, rather than one per service/product/project and a separate index page