Hey everyone!
The job board is already shaping up, things are looking neat so far and there's a thing or two to finish before we launch the MVP.
But there's a tiny issue - even though it already has a shape, we still should make it CLEAR what we want the website to be like before we launch it.
After talking to @with-heart about this, it makes sense to DEFINE what the ideal MVP should look and be like.
For that, it would be great if we develop a roadmap for the job board, starting with WHAT the MVP should have at first and HOW we can achieve that (a step-by-step list).
With that in mind, let's get into a few points I had in mind:
ACCESS TO THE JOB BOARD
The job board MVP should be only for DAO members first. This way we can iterate faster without having so many people using the site (and get feedback directly on the Discord). Of course, we may need to develop a way to authenticate those who own an NFT.
Later, if we decide to open the job board for everyone, this authentication feature could help us identify who belongs to the DAO via tags or icons, for example.
NOW, how should people authenticate? According to what we first had in mind, authenticating via Metamask using Supabase to store data would be a decent approach. This way we aren't entirely web2 and we have a way to authenticate only members from the DAO if we want.
What do you guys think?
JOBS
With the previous point in mind - we should decide whether we want the MVP to have both Gigs and Jobs, or only Jobs. So far, I've seen people asking for help in personal projects (gigs) and others posting job opportunities on companies they're working on (jobs) on the #jobs
channel in Discord. Of course, having both Gigs and Jobs will be a bit more of work, but it also makes the site more complete.
What are your thoughts on this?
P.S. We already have both pages almost completely done.
GIGS
For Gigs, we also need to figure out how the application form/website flow looks like. Gigs should have their internal application through the site.
Now, how can we ensure devs get paid for their work? Or at least they get a reward for their efforts?
Most bounty systems I've seen so far have their internal payment systems (with their coin). We should probably develop something like that.
Because of this, there are two paths (IMO) we can take:
-
A reward/payment system is a lot of extra work, and we still don't have a coin to work with, so we should probably delay the Gigs
part of the website for now and focus on the Jobs
board instead.
-
Otherwise, we could use the Gigs page to help people looking for help to connect with those who want to help (without a payment/reward system... yet).
APPLICATIONS
How does the application feature look like for Jobs
and Gigs
?
For Jobs
, my first idea was to let companies and people opening job posts add their email/webpage posts so devs can apply to jobs DIRECTLY and leave the job board only for posting. Now... should we also develop an internal tool for these applications? This will let companies see who applies through the job-board site - separating DAO members from everyone else who applies directly on their page/email.
For Gigs
, I explained a quick approach on Issue #26
. In short, add a simple application form with a proposal input (where devs write what they offer), proof they can handle the job (with links to repos/websites/etc), and a plan form where they explain how they will tackle the gig.
DESIGN
The first few pages in what we already have for the job board were designed taking into consideration the main developerdao.com site as an example.
The colors, boxes, shadows, and fonts were all taken from there. However, it probably doesn't look perfect for the job board. We should probably strive for something simpler (especially now the main DevDAO website is getting a re-design).
I'd suggest proceeding with a simple black-and-white theme instead of the current bluish/grayish tones in the site.
HAVING SAID THAT, we should probably develop a design system. This would be the job of the #design-guild
back at the Discord. Once we have the MVP rolling, that re-design may come helpful to make everything clearer. (Or maybe even before the MVP rolls out?).
Anyway, we're taking feedback + recommendations for this. If you belong to the DAO and want to give your two cents, feel free to comment on this issue.
DEADLINES
Also, we should probably come up with a deadline for the MVP. Not to put pressure on ourselves, but developing stuff without a clear date and/or idea of what we want to do could make it impossible to finally ship. However, it shouldn't be something too close either (most of us have either full-time jobs or other responsibilities).
I'd propose getting the MVP rolling within 2 weeks. This way everyone has enough time to contribute while also giving us enough space to test stuff out before releasing it.
The website is pretty simple still, but 2 weeks seems like a fair timeframe - right? What does everyone think?
ROADMAP
The points above are mostly my concerns + ideas so far. Once we figure them out (preferably within a few days), we can proceed with the writing of the roadmap so we're all in the same page when it comes to designing and developing the website.
Now, how should we write the roadmap? I propose creating a ROADMAP.md
in the repo. Whatever we end up having a consensus on, we'll write on that roadmap.
To speed up the roadmap process, I'd propose the following step-by-step list for the MVP roadmap:
-
-
-
-
After that, maybe we can come up with newer features over time - but that's probably enough for now. The re-design will take the site to a new place, so we may still have a lot of stuff to play around with + develop.
Anyway, this is my initial approach to a roadmap + concerns + ideas I think could help us develop the site further.
What do you guys think? @with-heart @carlomigueldy @Dhaiwat10 @miralsuthar @JoviDeCroock @swetshaw
Feel free to comment on every/any subject I went over. Also, it'd be great to come up with your roadmap so we can brainstorm as we go.
Consider Carlo's approach: Issue #33