README

JSON Résumé builder for PHP

A PHP library for building a JSON Resume.

JSON Resume is a community driven open source initiative to create JSON-based standard for resumes.

You can create a public Gist on GitHub, then add your username the JSON Resume registry URL to generate a nice-looking CV / resume, for example:

https://registry.jsonresume.org/YOUR_GITHUB_USERNAME

Different themes are available at jsonresume.org/themes/.

Installation

PHP 8.1 or above is required.

To install via Composer:

composer require elliotjreed/json-resume

Usage

<?php

require 'vendor/autoload.php';

$resume = (new \ElliotJReed\JsonResume\Entity\Resume())
    ->setBasics((new \ElliotJReed\JsonResume\Entity\Basics()
        ->setName('Elliot Reed'))
    ->setWork((new \ElliotJReed\JsonResume\Entity\Work())
        ->setName('Company Ltd.')
        ->setPosition('Spatula Tester')));

$jsonResume = new \ElliotJReed\JsonResume\JsonResume();

echo $jsonResume->asJson($jsonResume);

The PHP entities mirror the JSON Resume standard found at jsonresume.org/schema.

Getting Started with Development

Installing Composer

For instructions on how to install Composer visit getcomposer.org.

Installing

After cloning this repository, change into the newly created directory and run:

composer install

or if you have installed Composer locally in your current directory:

php composer.phar install

This will install all dependencies needed for the project.

Henceforth, the rest of this README will assume composer is installed globally (ie. if you are using composer.phar you will need to use composer.phar instead of composer in your terminal / command-line).

Running the Tests

Unit tests

Unit testing in this project is via PHPUnit.

All unit tests can be run by executing:

composer phpunit

Debugging

To have PHPUnit stop and report on the first failing test encountered, run:

composer phpunit:debug

Static analysis

Static analysis tools can point to potential "weak spots" in your code, and can be useful in identifying unexpected side-effects.

Psalm is configured at its highest levels, meaning false positives are quite likely.

Static analysis tests can be run by executing:

composer static-analysis

Code formatting

A standard for code style can be important when working in teams, as it means that less time is spent by developers processing what they are reading (as everything will be consistent).

Code formatting is automated via PHP-CS-Fixer. PHP-CS-Fixer will not format line lengths which do form part of the PSR-2 coding standards so these will product warnings when checked by PHP Code Sniffer.

These can be run by executing:

composer phpcs

Running everything

All of the tests can be run by executing:

composer test

Outdated dependencies

Checking for outdated Composer dependencies can be performed by executing:

composer outdated

Validating Composer configuration

Checking that the composer.json is valid can be performed by executing:

composer validate --no-check-publish

Running via GNU Make

If GNU Make is installed, you can replace the above composer command prefixes with make.

All of the tests can be run by executing:

make test

Running the tests on a Continuous Integration platform (eg. Github Actions)

Specific output formats better suited to CI platforms are included as Composer scripts.

To output unit test coverage in text and Clover XML format (which can be used for services such as Coveralls):

composer phpunit:ci

To output PHP-CS-Fixer (dry run) and PHPCS results in checkstyle format (which GitHub Actions will use to output a readable format):

composer phpcs:ci

Github Actions

Look at the example in .github/workflows/main.yml.

Built With

License

This project is licensed under the MIT License - see the LICENCE.md file for details.

elliotjreed / json-resume

Maintainers

Details