Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A markdown driven, single page CV for developers.

A customizable Jekyll portfolio theme with about, portfolio, and tools sections, easily configured via _config.yml.
namecard is a Jekyll theme that turns a single markdown file into a one-page CV website, designed for developers who want a low-maintenance resume site.
namecard is a markdown-driven, single-page Jekyll theme for creating a CV or resume website. It takes markdown content as input and generates a static HTML page as output on any Jekyll-based site, with most content and styling editable directly in markdown. The theme was created by the GitHub user afterdusk and is distributed under the MIT License.
gem "namecard" in your Gemfile and theme: namecard in _config.yml, and as a GitHub Pages remote theme using remote_theme: afterdusk/namecard._site folder.Installation follows Jekyll theme conventions. For GitHub Pages, add remote_theme: afterdusk/namecard to your _config.yml and uncomment the github-pages gem in your Gemfile. For gem installation, add gem "namecard" to your Gemfile, set theme: namecard in _config.yml, and run bundle. After that, edit the markdown content file to write your CV.
namecard is free and open source under the MIT License. There are no paid tiers or premium features mentioned on the page.
namecard is free and open source, released under the MIT License, so you can use, modify, and distribute it without charge, including for commercial purposes.
Yes. Use the remote theme method by setting remote_theme: afterdusk/namecard in your _config.yml. The gem installation method does not work directly with GitHub Pages builds; you must build locally and push the _site folder.
Editorial content and most styling are markdown-driven, so you edit the markdown file(s) that define the CV. For deeper theme changes, you can clone the repository and edit the templates directly, as recommended by the author.
Two methods are documented: adding the namecard Ruby gem for local builds, or using the GitHub Pages remote theme. The remote theme is simpler for deployment on GitHub Pages, while the gem requires a local build and push of the output folder.
