gets by

gets by is a collection of stories about living with a mental illness, as told by the tech community. Find out more. Want to read interviews in your favourite feed reader? Subscribe using RSS.

Contributing to gets by

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.

For Non-Coders

If you’re not comfortable with Github, editing markdown files, and Ruby gems, that’s totally fine. Just send an email to paddy@secondbit.org containing the following information. Feel free to omit anything you aren’t comfortable sharing.

  • Your name: how you want this attributed to you. If you want to be anonymous, just say so.
  • A picture of you: this should be something that you identify with. If you want to be anonymous, pick an image and we’ll use that, instead.
  • A brief (one or two line) bio: this will be used under your name to give context on who you are. Feel free to include links!
  • If you use social media (Twitter/Google+/App.net/Facebook) and would like your account linked to this interview, let us know which service it’s on and what your username (Twitter/App.net/Facebook) or account ID (Google+) is, and we’ll link it.

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.

  • Diagnosis: what do you deal with? How were you diagnosed? What prompted you to get tested for it? If you self-diagnosed, that’s fine; we’re not here to judge who “really” has an illness. If you think you qualify, you do.
  • Medication: what do you take? Does it help you? What are the side-effects? What stories do you have about it? How do you feel about it?
  • Challenges: how does your illness make your life harder? What stories do you have? What do you struggle with?
  • Strategies: how do you work through the challenges? What are some of the tricks you’ve learned to manage things?

Email all that to paddy@secondbit.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.

For Coders

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.

  • layout: this should always be interview.
  • name: how you want this attributed to you. If you want to be anonymous, just write anonymous, though know your Github username will be attached.
  • image: the filename of your image, without the path. For example, paddyforan.jpg.
  • intro: a brief (one or two line) bio that will be used under your name to give context on who you are. This is parsed as Markdown, so feel free to include links.
  • twitter: your Twitter username, if you want this linked to your Twitter account. Note that only one social media account should be specified.
  • adn: your App.net username, if you want this linked to your App.net account. Note that only one social media account should be specified.
  • googleplus: your Google+ user ID number, if you want this linked to your Google+ account. Note that only one social media account should be specified.
  • facebook: your Facebook username, if you want this linked to your Facebook account. Note that only one social media account should be specified.

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.

  • Diagnosis: what do you deal with? How were you diagnosed? What prompted you to get tested for it? If you self-diagnosed, that’s fine; we’re not here to judge who “really” has an illness. If you think you qualify, you do.
  • Medication: what do you take? Does it help you? What are the side-effects? What stories do you have about it? How do you feel about it?
  • Challenges: how does your illness make your life harder? What stories do you have? What do you struggle with?
  • Strategies: how do you work through the challenges? What are some of the tricks you’ve learned to manage things?

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.