search

junior-dev-struggle-bus / juniordevstrugglebus

Website for the Junior Dev Struggle Bus Meetup
https://www.juniordevstrugglebus.com
MIT License
9 stars 18 forks source link

Add "Current Projects" section to the website #23

Open nspilman opened 5 years ago

nspilman commented 5 years ago

We have a lot going on, and should have a place to keep track and show off our work.

Xoadra commented 5 years ago

I talked to @bhurstGH about an idea related to this that I've been thinking about working on. I don't know if it would be an extension of the current website or relegated to an alternative app and/or URL, but I do want to help create a hub that allows for easier visibility and ease of contribution to the community projects. Either way though, it would be connected to the website in some fashion no matter what like the blog is.

I'm still fleshing out the idea a bit but when I have a more solid idea of what to do, I'll let you know and share my notes on the subject. Feel free to toss me your ideas on the matter in the meantime.

nspilman commented 5 years ago

Completely with you. I'm thinking we need an application with api endpoints for the data our website(s)

nspilman commented 5 years ago

https://github.com/junior-dev-struggle-bus/juniordevstrugglebus/issues/30 Is the relevant issue, actually.

Xoadra commented 5 years ago

If we want to analyze information from GitHub, the GitHub API is a great candidate for that. We could also just hardcode the data in if that's what you're thinking by referencing issue #30, but it may be better to build something that can be updated on its own or through form submissions vs. having to manually code things in each time an update is needed.

nspilman commented 5 years ago

This sounds like an infrastructure move, which is exactly the sort of moves I’m looking for. Are you comfortable moving forward with gh api integration?

Xoadra commented 5 years ago

I'm comfortable getting acquainted with the Github API. I've only used it loosely thus far to grab info on personal repos, but this can be extended to include other things that directly interact with the organization's repos, authenticate users, etc.

Infrastructure makes things a tad more complicated. Anything that does more than just read content will need to be server-side. If I understand this properly, both the blog and main site are hosted on Netlify as static sites, right? To extend this to some of the GitHub integrations I have in mind, we would need to use something like Netlify Functions.

Data storage and hosting are two other considerations. Netlify has an addon for data storage using FaunaDB if you want to check it out. It might be a good option for us and has free usage tiers too.

nspilman commented 4 years ago

@Xoadra This issue is tied to JDSLab, yeah? What's the word there?