Initial job board postings

[cannikin]

We're planning on including a dead-simple job board on the new site. It would be great to launch the site with a few job listings already prepared. Let's talk to the folks in the startup club Slack channel and if any are hiring we could get a job listing from them.

We're also thinking of adding a "job seekers" section where you can list yourself as a Redwood developer looking for work. We could open this up to the community at large to add themselves and we should have a nice list at launch.

[noire-munich]

We're also thinking of adding a "job seekers" section where you can list yourself as a Redwood developer looking for work. We could open this up to the community at large to add themselves and we should have a nice list at launch.

Subscription by email on a dedicated page/widget? QR code? contest based enlistment ? viral bot on discord? :D Early recruitment is a good opportunity to build up some hype, let's be daring and creative x)

[cannikin]

I was planning on asking in the #startup-club channel if anyone's currently hiring and give them access to fill out a listing somewhere. Likewise for listing yourself for hire, start with the #general channel, post something on Discourse, Discord, Twitter, mention at the next few zoom community meetups...not sure where else we can let people know about it before it launches on the site for real. But I guess that's why I'm not in marketing!

[realStandal]

@cannikin DT wanted to include an "Open Positions" section on a startup's showcase page.

This is my first swing at what the info-card for that section would look like.

What I'm thinking is, I make that card into its own component and a startup's positions can be a combination of:

• Static positions which are just "hard-coded" implementations of that component.
• A Cell which queries the database, listing all Jobs where company is the startup.

I've only glanced at what you've just pushed for the Jobs section; so, my question is: does that sound like a good choice, or am I better leaving this list static until the job section is a bit more stable?

The biggest difference I see is that your locations are stored as just a list and includes remote; I had the assumption remote would be its own field - and then the inclusion of experience with RedwoodJS as a requirement. That's no biggie to include as one line in the design though (and I'm tempted to correct it now).

[realStandal]

I definitely wasn't thinking of validation and the whole nine; a lot more than is needed here. Are you just leaving it up to scout's honor not to throw a # Location in the mix? I like the li::after for listed locations, thanks!

I think all the jobs should imply that the person either needs to know Redwood, or be willing to learn it, so I don't know that we really need to call that out—that's the whole point of the job board! :)

It wasn't to imply Redwood being a part of the job or not, it was to let the person applying know experience with Redwood beforehand would be required/favored. 🤷 was an idea.

[cannikin]

I think you can put an allow-list in most markdown renderers?

I'd like to keep the job listing super simple to start and see what people think. We may get some requests right off the bat from people listing their jobs, and this might be one of them!

[realStandal]

Second go at job card.

I kept the design simpler and took some inspiration from how you're using the data. I made a second showcaseJobs() resolver instead of adding company search to the existing jobs(). I figured it's easy enough to swap over and I didn't want to make any choices for you.

[cannikin]

Nice! Very simple, love it! I have no idea what the final design is going to end up being (I saw mention in the channel of an outside designer possibly taking a look?) but this is a really flexible base if we end up going in a wildly different design direction.

[cannikin]

I’ve been pushing up the job board as I’ve been working on it if you want any references. Running the db seed will give you some job posts and job profile posts.