Skip to content

Portfolio content

10x Resume portfolio content is an collection of files and documents a candidate shares with a reviewer for a specific enquiry. Reviewers must provide the correct link and password to access portfolio content.

When a reviewer successfully opens an enquiry link with the proper password, 10x Resume downloads an index of the enquiry files and renders a menu and welcome page. As the reviewer navigates from page to page 10x Resume downloads and renders associated portfolo content.

10x Resume portfolio content is kept in two directories below Job/Portfolio/Src:

  • 10x - markdown pages
  • 10x-files - related assets and documents

Candidates may customize these files for each enquiry.

10x

  • Directorydev
    • DirectoryJob
      • DirectoryPortfolio
        • DirectorySrc
          • Directory10x ◀─────── source markdown files
            • hello.1.md
            • background.1.md
            • position.1.md

The 10x markdown pages hold the text for the top level welcome page and every page reachable from each item or section in the menu.

Most 10x files in the example data are similar to requirement.01.md which contains a small amount of frontmatter metadata and markdown text.

Example - requrement.01.md
---
title: Bring new features from conception to completion
layout: Plain.html
permalink: /10x/requirement.01.html
resources:
  - id: 1
    kind: requirement
    html: requirement.01.html
    description: Bring new features from conception to completion,
                 helping people around the world to learn more effectively
                 by contributing code across our entire stack.
    years: 18
    experience:
      - 2013-2014 # 2 Quarum Labs
      - 1998-2000 # 3 Saratoga Systems
      - 1992-1994 # 2 Illustra
      - 1991-1992 # 1 Scopus
      - 2017-2020 # 4 Cisco Hyperflex
      - 2016-2017 # 2 Cisco Metacloud
      - 2012-2013 # 1 Galiam
      - 2009-2011 # 3 Infinium
---

<p style="margin:10px;"></p>

In the 8 years I spent at Quorum Labs, Saratoga Systems, Illustra and
Scopus Technologies I owned significant end-to-end projects from start
to finish. I spent 5 years working with geographically distributed
development teams at Cisco and before that I spent 2 years managing
distributed engineers, operators and DBAs at Galiam and Infinium.

However a few pages such as position.1.md contain only frontmatter. For these 10x-files has all the content.

Example - position.1.md
---
title: Position
layout: Plain.html
file: /10x/position.1/Brilliant_-_Product_Engineer.html
resources:
  - id: 1
    kind: position
    html: position.1/index.html
    icon: icons.1/brilliant.png
    dark: icons.1/brilliant_dark.png
    width: 300px
    iframeindex: Brilliant_-_Product_Engineer.html

  - id: 1
    kind: position_zip
    subdir: position.1
---

These markdown files are explained in the Customizing an enquiry section.

10x-files

  • Directorydev
    • DirectoryJob
      • DirectoryPortfolio
        • DirectorySrc
          • Directory10x-files ◀──── source assets and documents
            • Directoryicons.1/
            • Directorybackground.1/
            • Directoryposition.1/

Directories below 10x-files contain additional content associated with the corresponding markdown pages in the 10x directory.

For example, 10x-files/position.1 holds a number of html files and assets describing a position at Brilliant ↗︎.

  • Directorydev
    • DirectoryJob
      • DirectoryPortfolio
        • DirectorySrc
          • Directory10x-files
            • Directoryicons.1/
            • Directorybackground.1/
            • Directoryposition.1/
              • Brilliant_-_Product_Engineer.html
              • DirectoryBrilliant_-_Product_Engineer_files
Example - position.1 (rendered)

build

  • Directorydev
    • DirectoryJob
      • DirectoryPortfolio
        • Directorybuild
          • Directory10x ◀────────────── json and content bundles
            • _items.json
            • hello.1.md
            • position.1.zip

10x Resume uses 11ty ↗︎ to render the candidate’s portfolio content into static html. The output is written to the Job/Portfolio/build directory. The rendered html is bundled along with related assets, documents and work samples. The bundles are indexed with json files organized for transfer to Userbase.