Page for each project

[sumnerevans]

Not sure if we need this, someone really needs to do some design work to:

1. determine if it's necessary
2. determine what information would be displayed on each project page, and what subset would be displayed on the project listing page
3. determine what it would look like
4. determine the impact of this on the database schema
5. any other considerations

Currently we just have a list of projects. If we add more information about each project, it will start to get cluttered. Having individual pages for each project to show more details would reduce the clutter.r

Things to include on each page

• Project Title
• Project Description
• Project Members
• Person to contact
• Technologies used

Considerations

• Maybe we should include a way to link Wiki pages to projects and link them here.
• Or maybe this should be implemented as Wiki pages.
• ~We need to figure out the URL scheme. /p/<project_id> would probably be the most consistent, but I don't really like it. I would prefer /projects/<project_id>. (See https://github.com/ColoradoSchoolOfMines/acm-website/pull/35#discussion_r162169666.)~
• Consider renaming the current ProjectsController to ProjectListController. This will allow us to use ProjectsController and ProjectController as the lookup controller and project page controller, respectively. (See https://github.com/ColoradoSchoolOfMines/acm-website/pull/35#discussion_r162391969 for context)

Design

• URL scheme: /p/<textual_id>.

[liamwarfield]

I feel like each page could include:

• Project Title

• Project Description

• Project members

• Looking for XXXXX skill

• Join group button/person to contact

• Maybe some way to show off Progress

[jackrosenthal]

We need to figure out the URL scheme. /p/ would probably be the most consistent, but I don't really like it. I would prefer /projects/. (See #35 (comment).)

Continue use of short URLs please.

[jackrosenthal]

URL scheme: /p/.

ID should be textual, rather than appealing to the database model. You might need to add an extra column for that textual ID.

Just like users page is /u/user_name, not /u/uid_number

[sumnerevans]

Should that textual ID be the primary key or should there be an id and a textual_id field (obviously both fields would not allow duplicates)?

[sumnerevans]