Expand to encompass all opensource at UCLA

[BryanPan342]

[Use Case]
Create a website that highlights opensource at UCLA and acts as a centralized location for the going-on of tech across UCLA.

The current structure of the repository lends itself to be shared across multiple organizations. Wouldn't it be phenomenal to have any organization at UCLA showcase their opensource projects? It would be a great place for new students, older students, alumni, recruiters, and professors to see what exactly UCLA is up to.

[Proposed Solution]

Utilize a PR (opt-in) mechanism for organizations to display their projects on the site.

Process

• PR to add a new config to the repository
  • Specify route (website.com/[slug])
  • Add tags and organization information (name, github, etc)
  • Choose a type of data retrieval (yml, contentful, json, strapi, netlify cms, google sheets)
• Aggregate your orgnanization's data in your chosen content model
• Customize: create custom templates, css frameworks, whatever to showcase your organization and club

Example configuration:

slug: cl
org_name: Creative Labs
website: https://creativelabsucla.com/
github: UCLA-Creative-Labs

data: contentful
contentful_delivery_token: xxxXXXxxx         // These can be public because they are simply delivery
contentful_space_id: xxx

We would need to do some nifty development to inject custom css / javascript into a dynamic route, but it seems like a good challenge.

I also would be down to do some sort of liquid markdown!

---
slug: cl
org_name: Creative Labs
website: https://creativelabsucla.com/
github: UCLA-Creative-Labs

data: contentful
contentful_delivery_token: xxxXXXxxx         // These can be public because they are simply delivery
contentful_space_id: xxx
---

# Code

[insert code block here]

# Styling

[insert code block here]

[BryanPan342]

@mattxwang ^ kinda what we talked about but written down

[BryanPan342]

Also lowkey wish i could make this an RFC so we could see how the doc develops but this is fine I guess

ALSO, totally okay if you don't want to go in this direction for the repo!! This is ACM material so IF you want to do something like this, I would be really down to build something up!

I think it would be good especially for new students or people breaking into tech to see what is available for them to look at and join. Breaking down as many barriers into tech as possible and hopefully bringing the tech community at UCLA to a centralized location.

@emmyc even said it might be cool to have a forum for people to ask questions about starting projects?? But I think that is a loooong term idea

[mattxwang]

Realizing that we talked about this over messenger but never put it in writing (publicly).

Broadly, I am very down for this idea. I'm still unsure if people should be adding on to our project directly, or cloning our project and updating the parameters. This may warrant a larger repository, which I think may make more sense to work on once I sit down a bit and really figure out how this one will work for ACM (right now, my biggest worry is getting and maintaining the project data in some easy to do and useful way).

(this can also be a part of our larger initiative with Prof Eggert re: that OSS portal)

Also lowkey wish i could make this an RFC so we could see how the doc develops but this is fine I guess

How interested are you in this? We could co-author an RFC, plop it in the CL repo, and see if I can garner some support from us + Nova, Blueprint, etc.

[BryanPan342]

How interested are you in this? We could co-author an RFC, plop it in the CL repo, and see if I can garner some support from us + Nova, Blueprint, etc.

I'm down to go in on this