Contributing to gets by is an intensely personal decision, and something we want to make as easy and comfortable as we can for our interviewees. It’s hard to talk about mental illness, and we want our interviewees to feel safe as they do so. To that end, we will update or remove any interview at any time if the interviewee requests it. We will do whatever we can to respect their wishes, though some parts of the internet (caches, RSS readers, etc.) fall outside our reach. Anything we can do, we will; these are not our stories, and they’re not ours to make decisions about. We provide a platform to share your story; that’s all.
If you’re not comfortable with Github, editing markdown files, and Ruby gems, that’s totally fine. Just send an email to email@example.com containing the following information. Feel free to omit anything you aren’t comfortable sharing.
You should also include the content of your interview. Interviews are supposed to be narrative in format, and it works better if there are multiple paragraphs in each section. Feel free to include as much or as little information as you’d like. If you’re not comfortable talking about a section, just omit it.
Email all that to firstname.lastname@example.org, and we’ll get it converted into a file we can post. When that’s done, we’ll email you back a screenshot of what your post will look like on the site, for you to approve or request modifications to. We’ll modify things until you’re happy with them, and when you give the final go-ahead, then we’ll post your interview.
If you know how to publish to Github pages and are comfortable with your interview being seen before the official publication, you can send us a pull request with your file. Just fork the repo, create a new branch named for the shortlink you want (whatever comes before .getsby.co in your desired URL), and write your interview in the _posts folder. The naming convention is simple: YYYY-MM-DD-id.md. The YYYY is the year the post is written, the MM is the month the post is written, and the DD is the day the post is written. id is the ID for the post, which is what comes before getsby.co in the URL. The posts are written in Markdown, and the format is simple: each section is preceeded by the section name as an h2 (## in markdown). If you put a > before a pargraph, it’s treated as a pull quote—you can see some in action on https://paddyforan.getsby.co. Also, save the image you want to use in img/people named after your ID. For example, /img/people/paddyforan.jpg. Finally, include the following metadata in the YAML header—feel free to omit anything you aren’t comfortable sharing.
Your file should now look something like this. The body of the post is just the content of your interview, as Markdown. Interviews are supposed to be narrative in format, and it works better if there are multiple paragraphs in each section. Feel free to include as much or as little information as you’d like. If you’re not comfortable talking about a section, just omit it.
You can run `jekyll serve` to preview your interview (note that your interview will be found at http://localhost:4000/interviews/your-id-here, not your-id-here.getsby.co), and when you’re happy with it, just send a pull request. We may make some small modifications (highlighting quotes we think are resonant, making some typography corrections—e.g., changing ’ to ’—and just generally making the style consistent), which we’ll then pass back to you for approval. Once you give us final approval, we’ll merge your branch and push the updates to our live site.