I started with raw HTML, but wanted to have an interface that wouldn't require FTP-ing / SSH-ing, etc., so I played with a Gist as a datastore (example JSON: https://gist.github.com/charliepark/5037450; explanation of how I used it: https://gist.github.com/charliepark/5055709), but realized I wanted a little more flexibility. So I quickly hacked together a WordPress template so I could submit entries, where they could be filtered ("featured" and "not featured"), and they'd get cleaned up automatically (14 days on the page for not-featured posts, 1 month for featured posts). So maybe not quiiiite as MVP as I could have gone, but it was a good quick lesson in WordPress hacking. Side note: I'm happy to report that, with caching, WordPress pages can handle HN levels of traffic without a problem.
Initial inventory was a combination of seeing posts on other job boards, poking around at companies I know are remote-friendly, and seeing the "hiring" thread on HN last week. In terms of inventory, I'm hoping to highlight jobs that are already posted at other job boards as well as posting original ones. I'm curious to see how this chicken/egg problem resolves. I have a few thoughts, but we'll see.
Thanks for the encouragement on the UI. I'll keep fiddling with it to see what I can do to make it more legible without killing the spirit of the page.
I started with raw HTML, but wanted to have an interface that wouldn't require FTP-ing / SSH-ing, etc., so I played with a Gist as a datastore (example JSON: https://gist.github.com/charliepark/5037450; explanation of how I used it: https://gist.github.com/charliepark/5055709), but realized I wanted a little more flexibility. So I quickly hacked together a WordPress template so I could submit entries, where they could be filtered ("featured" and "not featured"), and they'd get cleaned up automatically (14 days on the page for not-featured posts, 1 month for featured posts). So maybe not quiiiite as MVP as I could have gone, but it was a good quick lesson in WordPress hacking. Side note: I'm happy to report that, with caching, WordPress pages can handle HN levels of traffic without a problem.
Initial inventory was a combination of seeing posts on other job boards, poking around at companies I know are remote-friendly, and seeing the "hiring" thread on HN last week. In terms of inventory, I'm hoping to highlight jobs that are already posted at other job boards as well as posting original ones. I'm curious to see how this chicken/egg problem resolves. I have a few thoughts, but we'll see.
Thanks for the encouragement on the UI. I'll keep fiddling with it to see what I can do to make it more legible without killing the spirit of the page.