Overview
100 devs is a fast-growing community of developers going from 0 to hired in less than a year. It would be ideal to have some structure in place for those who have gone through the course material and are job-ready.
The 100devs community is building a lot of momentum and there will be a point where the talent pool coming out of 100devs could not be ignored. 100devs could use a talent showcase page on a website to make it easier for employers interested in hiring to bring opportunities to the community.
For this RFC, I'd like to propose what the talent showcase could look like and gather feedback on the tech stack and/or approach in technological choices and implementation.
As far as my involvement goes, I'd like to at least kickoff and oversee the project and leave it to the project team to tidy things up. I'll also be around for troubleshooting.
Tech Stack
Next is easier to dive into, it's really mostly React with a few APIs specific to Next. 70% of the React ecosystem is built on Next, it's the dominating React framework of today.
Gatsby has more complicated parts, it's tightly integrated with GraphQL but this allows it to consume any source of data to be used anywhere throughout the site with ease. I'm a fan of both, but I might end up learning more towards Next.js for this project in particular.
MDX allows you to write JSX within Markdown files, giving you the power of React. Markdown files are ideal because they are easy to produce. Anyone can make a markdown file off their computers or even use online Markdown editors. This is a cost-effective approach that allows us to not worry about integrating with some other platform for content.
The concerns around this approach would be the inability to handle some kind of form validation to fill out or create these markdown files, this is something I'd like to look into, though so will report back on that.
- Tailwind?
I've never used Tailwind but people seem to be very excited about it, at least we'll know things will look great. Not very picky when it comes to styling libraries tbh so whatever is comfortable to the project team, I'd rather go with that. I prob won't be doing a lot of styling tbh.
Similar Projects
The resilient coders demo day site is a perfect example of what we should go for. I happened to have built this myself as well:
https://demoday.resilientcoders.org/boston/
We should have the same exact format for showcasing 100devs students. Are all the hiring partners going to be 100% remote? Perhaps we might need a filter for regions? What are your thoughts?
Long Term
This is going to be a relatively low-effort dash to an MVP. If this goes well enough, perhaps we can move to a real platform experience where 100devs would provide an authentication flow for each student. There has also been some discussion about companies getting a 100devs job board available for them to post to, we'll cross that bridge when we get there, though.
Providing Feedback
Feel free to ask any questions or call anything out here on this issue!
Overview
100 devs is a fast-growing community of developers going from 0 to hired in less than a year. It would be ideal to have some structure in place for those who have gone through the course material and are job-ready.
The 100devs community is building a lot of momentum and there will be a point where the talent pool coming out of 100devs could not be ignored. 100devs could use a talent showcase page on a website to make it easier for employers interested in hiring to bring opportunities to the community.
For this RFC, I'd like to propose what the talent showcase could look like and gather feedback on the tech stack and/or approach in technological choices and implementation.
As far as my involvement goes, I'd like to at least kickoff and oversee the project and leave it to the project team to tidy things up. I'll also be around for troubleshooting.
Tech Stack
Next is easier to dive into, it's really mostly React with a few APIs specific to Next. 70% of the React ecosystem is built on Next, it's the dominating React framework of today.
Gatsby has more complicated parts, it's tightly integrated with GraphQL but this allows it to consume any source of data to be used anywhere throughout the site with ease. I'm a fan of both, but I might end up learning more towards Next.js for this project in particular.
MDX allows you to write JSX within Markdown files, giving you the power of React. Markdown files are ideal because they are easy to produce. Anyone can make a markdown file off their computers or even use online Markdown editors. This is a cost-effective approach that allows us to not worry about integrating with some other platform for content.
The concerns around this approach would be the inability to handle some kind of form validation to fill out or create these markdown files, this is something I'd like to look into, though so will report back on that.
I've never used Tailwind but people seem to be very excited about it, at least we'll know things will look great. Not very picky when it comes to styling libraries tbh so whatever is comfortable to the project team, I'd rather go with that. I prob won't be doing a lot of styling tbh.
Similar Projects
The resilient coders demo day site is a perfect example of what we should go for. I happened to have built this myself as well:
https://demoday.resilientcoders.org/boston/
We should have the same exact format for showcasing 100devs students. Are all the hiring partners going to be 100% remote? Perhaps we might need a filter for regions? What are your thoughts?
Long Term
This is going to be a relatively low-effort dash to an MVP. If this goes well enough, perhaps we can move to a real platform experience where 100devs would provide an authentication flow for each student. There has also been some discussion about companies getting a 100devs job board available for them to post to, we'll cross that bridge when we get there, though.
Providing Feedback
Feel free to ask any questions or call anything out here on this issue!