jsonresume-theme-stackoverflowed

A JSON Resume Theme inspired by the Stack Overflow Developer Story resume format.

Motivation

Sadly the Stack Overflow team decided to discontinue the Jobs and Developer Story platform on March 31, 2022. Having had much career success particularly thanks to their product this came as disappointing news - there is something about this resume format that seems to translate well with recruiters, so with a little artistic license this project aims to create a faithful replica that is compatible with the Resume CLI tool.

Sample

Getting Started

Start a new project and install the following dependencies.

npm install resume-cli jsonresume-theme-stackoverflowed

Optionally generate some sample data if not starting with an existing resume.

npx resume init

Add some workflow scripts to the package.json

{
    "scripts": {
        "validate": "resume validate --resume ./resume.json",
        "serve": "resume serve --resume ./resume.json --theme stackoverflowed",
        "export": "resume export --resume ./resume.json --theme stackoverflowed",
        "pdf": "$npm_execpath run export -- --format pdf \"./$(date +'%Y-%m-%d').pdf\"",
        "html": "$npm_execpath run export -- --format html \"./$(date +'%Y-%m-%d').html\""
    }
}

Happy job hunting...

npm run <script>

⚠️  Windows users: the resume-cli tool and puppeteer combo is difficult to get running in WSL and not reliable when generating PDFs - A linux virtual machine is recommended in this case.

Environment Configuration

StackExchange

This theme can make requests to fetch a short summary of contributor activity that will be displayed underneath a StackOverflow profile entry when a valid url is specified. By default this behaviour is switched off due to the API throttling, limiting anonymous requests to 300 per day. However this should be okay for occasional use and can be explicitly enabled by setting the key to anon.

STACK_EXCHANGE_API_KEY=anon
STACK_EXCHANGE_ACCESS_TOKEN=

Resume Configuration

The JSON Resume schema allows space for arbitrary meta data. This theme will consume a custom configuration from JSON defined under the following namespace, all further parameters listed on this page will assume that they are configured at this level. For the avoidance of doubt a sample configuration is available, which matches the default values if otherwise unspecified.

{
    "meta": {
        "theme-stackoverflowed": {
            /* configuration */
        }
    }
}

---

Localisation

{
    "locale": string
}

locale — string

A language (e.g. en) or regional variant (e.g. en-GB) that will localise dates and text content.

• defaults to en-US

---

Formatting

{
    "format": {
        "date": string,
        "location": string | string[]
    }
}

format.date — string

A date-fns format for rendering dates.

format.location — string | string[]

A template or list of templates (fallbacks) that will be passed the values of basics.location from the resume - interpolated keys use the syntax {{var}}. In addition to the schema properties, the following keys are also available.

Key	Description
countryNameAlias	A colloquial name resolved from the countryCode.
countryNameOfficial	A full country title resolved from the countryCode.

If it is preferable to split an address across multiple lines, this can be achieved by inserting a newline character in the template - note that this needs to be doubly escaped to be valid JSON.

{
    "format": {
        "location": "{{address}}, {{postalCode}} \\n {{city}}, {{region}}"
    }
}

Introduction

{
    "intro": {
        "avatar": {
            "align": string,
            "hidden": boolean
        }
    }
}

intro.avatar.align — string — "left" | "right"

By default the avatar will align to the right of the address and contact details - however can be configured to align to the left of the name and title.

intro.avatar.hidden — boolean

All resume data will be displayed by default, where content exists - if a profile image is not available, then this theme will lookup a Gravatar for the email listed under the basics profile data. However if it is preferable to hide a profile image then the hidden option can be set to true.

Sections

{
    "section": {
        [string]: {
            "order": number
            "break": boolean
            "hidden": boolean
        }
    }
}

Sections map directly to resume schema fields and the currently supported names are: skills | work | volunteer | projects | education | awards | publications | languages | interests | profiles | references. Sections are only rendered if there is sufficient data for each in a given resume.

section.<name>.order — number

Sections are by default laid out with the same priority as stated above - each section relevant to a resume will be assigned a number (starting from 1). This may be overridden on a per-section basis to customise the order.

section.<name>.break — boolean

Sometimes a page break may split a section in an awkward place - this is difficult to compensate for programmatically given the unknown nature of the configuration and / or data being rendered. As such, this escape hatch allows a section to force a page break (above) by setting it to true.

section.<name>.hidden — boolean

If it is preferable to maintain data in a resume but not have it rendered, a section can be disabled by setting this to true.