Package Exports
- jsonresume-theme-stackoverflowed
- jsonresume-theme-stackoverflowed/dist/render.js
- jsonresume-theme-stackoverflowed/dist/render.mjs
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (jsonresume-theme-stackoverflowed) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
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
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": {
            "show": boolean,
            "align": string
        }
    }
}intro.avatar.show — boolean
All resume data will be displayed by default, where content exists - however the profile image can
be hidden if preferable. If a profile image is not available, then this theme will lookup a
Gravatar for the email field under the basics profile data.
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.
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.