/projects: create collection page for each project

[bryceerobertson]

I think unlike the other databases, /projects warrants individual pages for each list item. Working on a project is a reasonably large commitment, meaning the user will need a reasonably large amount of info about it if possible. Additionally, the Description for projects vary a lot, and creating consistency in the length of those descriptions for the cards would sometimes mean deleting a lot of info provided by the person who had the idea. In those cases where there is a lot of info on the project, we should have a summary on the card and a full description on the collection page.

The collection page would also display other fields e.g. Chat, Contact, Stack. Other than the name and description (summary), the card would show Status.

[melissasamworth]

I'm intuitively inclined to agree. Want to collect more evidence for this one?

My current evidence

• dogfooding: I currently don't know where else to access a list like this, and I imagine if I do full-time work with AED I will reference something like this at least once and maybe often. In that case more details would be helpful.

Evidence I would like to see

• Bryce providing cases of himself using this list, and how he uses it
• Bryce providing evidence that other people in AED currently use this list, and how they use it

[bryceerobertson]

My dogfooding:
Currently I use the same list on alignment.dev to find ideas for what projects AED should consider building. I'm assuming evidence of using that list cross applies here, since it's the same data.

[bryceerobertson]

Update: decided against doing this for now.