Dev Team Page Projects

[mattxwang]

Our website now has information about ACM's Dev Team , but something else that we should have is more detail regarding the projects we do in a projects page (or add the information to the dev team page)!

Like most informational pages, creating a page requires more than just technical work - it's a team effort. This process will mimic what doing client work / working in a larger company might look like. Involved parties are:

• you, the developer(s)
• Matt + Evan + dev team director - checking the vision/copy/content
• ACM Design - helping with UI/UX, creating design elements
• everybody else on the dev team - to make sure it's representative of us!
• other people, if needed, to do user testing

The TODOS, including the ones completed in #309 are:

• [x] what is the ACM dev team? how is it different from committee's dev teams (Hack, Teach LA), or just attending Hack events?
• [x] who can join? how do you join? do you need previous experience?
• [x] who runs the dev team? who's in it?
• [x] what kind of projects do we work on? where would you find them?
• [x] what kinds of technologies do we use?
• [x] is all of our code open-source (yes)? can anybody contribute (yes)? can you see our code (yes)?

TODOS when adding projects would be:

• [ ] can we put a list of our projects in a JSON file, and then list them out card-by-card? we can include metadata about each project; see Teach LA's for example - this metadata could include primary language for code, links to the project and repo in a card format instead of paragraphs like it currently is
• [ ] do we want to hit GitHub's API to show activity, or last contributions? commit graphs? insights?

Out of the box ideas include:

• [ ] any dev-related easter eggs? ex putting an application in the JS console?

The workflow should be something like:

1. identify what you want to do - how the page should be structured, what should be added and where
2. with relevant stakeholders, create a skeleton layout
3. start getting content; this can happen asynchronously, and use placeholders in the meantime
4. component-by-component, flesh out sections of the page
5. on first draft, do some user research + consult ACM Design for UI/UX pointers
6. finalize & publish 🚀

Update: Dev Team Page is now up ( see #309 ) Re-scoped issue to be project specific

This is a very general ticket with a lot of room for how you want to do it! Basically, I don't like the idea of just using paragraphs for the Dev Team projects, so I'd like to switch that into a different layout.

[mattxwang]

@advaithg can you re-scope this ticket or do some sort of checklist so we can see what was resolved in #309 and what still needs to be done?

[mattxwang]

@advaithg can you re-scope this ticket or do some sort of checklist so we can see what was resolved in #309 and what still needs to be done?

Ping on this!

[advaithg]

Ping on this!

Just re-scoped it so it now becomes a generalized project page ticket! This could either be a general projects page for ACM as a whole or re-making the projects section of the dev team page to have a different (non-paragraph) layout that makes it clear how to access the projects.

If it's making a whole projects page for ACM in general, the idea would still be the same (come up with a layout that makes it clear on how to access projects, who maintains them, and what they're built on), but the dev-team page would stay as is and the new projects page would have dev team projects + other committee projects.

Either way the major part remains the same, so if whoever wants to work on this decides to just update the dev team page and we later decide to make a projects page we could still use their work!

[mattxwang]

I think we should just stick to the projects that the dev team works on, so it's a very clear "Dev Team" page. Plus, helps with recruitment!