Job Postings not updated on the Career page

[thaonguyenle]

Describe the bug When I go to https://blockstack.org/careers , the Director of Strategic Partnership/BD role is not listed on there. Or I can't see it. Same with Muneeb and Lauren. We were able to see it last week. However, Tom can see this role on his computer.

The role can be always be viewed here: https://jobs.lever.co/blockstack/d0b61b97-d8d7-446e-889b-7c6e8742521e. But. I don't want to post a tweet linking people to that, instead of our career page

We should have everyone be able to view these job descriptions on the career page.

Desktop (please complete the following information):

• OS: Mac OS Mojave
• Browser: Chrome

Additional context I'm trying to get Muneeb to post this JD on his Twitter soon so I would really appreciate this done soon-ish.

[wileyj]

https://api.lever.co/v0/postings/blockstack?mode=json

https://github.com/blockstack/blockstack.org/blob/master/common/es6/index.js#L106-L131

the missing job posting has a / char.

[markmhendrickson]

@aulneau can you confirm this role isn't getting imported due to the slash, and if so, whether there's a simple fix?

If there isn't a quick 5-minute fix here, I may recommend we resolve this implicitly when launching the new page on Webflow in the coming days.

[aulneau]

@markmhx as I stated in my email, the website fetches the jobs data at build time each time we deploy the site. That means that if there are jobs added to lever after a deployment, the data will not exist on the site until a redeployment happens. I just tested it locally, and these are the jobs I see:

Part of why this is the case is because for a long time, we as a company didn't want the site to be able to be updated without our knowledge, and as such, we went the route of doing a static export of the site for each deployment. There have been a lot of improvements to next.js, such as Incremental Static Regeneration, which the ui docs use and new docs will use, but because we are moving away from next.js for blockstack.org, that was never implemented.

Anyways, that's all to say that if there is a new job posting, we only have to ask someone from devops to initiate a redeployment of the site and it will fetch the latest data from lever.

However, Tom can see this role on his computer.

To be honest I have no idea why this would be the case.

@wileyj could you do a fresh deployment of blockstack.org? That should resolve this issue.

[markmhendrickson]

Got it, I figured this was a separate issue since the other three are here, but that makes sense 👍

[thaonguyenle]

But I'm pretty sure I saw it last week? is that not real (what I saw? Maybe I was imagining it?)

Thanks @wileyj for doing this. Pls let me know when it's ready.

On Wed, Jul 8, 2020 at 10:28 AM Mark Hendrickson notifications@github.com wrote:

Got it, I figured this was a separate issue since the other three are here, but that makes sense 👍

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/blockstack/blockstack.org/issues/1126#issuecomment-655555467, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJJVFE56E6J4X7BRFCZDQEDR2R7CFANCNFSM4OTHYNRQ .

[markmhendrickson]

👻's in the machine...

[kantai]

For those that are curious -- for exactly the reasons that @aulneau mentioned, there's the potential for a skew between the static exports and dynamically constructed pages on the site, so if you go to blockstack.org and the click about->careers from the home page, you should see a dynamically fetched list of jobs (with the new listing), but if you refreshed the page, you'd see the static build (without the new listing)

[wileyj]

I would argue that this process should be changed. i don't think we should have to rebuild the site every time a listing is changed - it requires more process, and if a role is added/removed it requires someone to rebuild the site again.

at the very least, for this json fetch i think it would suit us better to simply retrieve the data when the /careers endpoint is requested.

[markmhendrickson]

This process is getting changed with the move to Webflow next week, so I think we just need one last rebuild here to fix the missing role for the next several days.

[markmhendrickson]

This has been resolved