The Hacked-Together Spaghetti Code for the EVE Online SPA Trading Site
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github v6.0 Feb 18, 2019
_includes/home v6.0 Feb 18, 2019
_layouts v6.0 Feb 18, 2019
css v6.0 Feb 18, 2019
dist v6.0 Feb 18, 2019
downloads v6.0 Feb 18, 2019
images v6.0 Feb 18, 2019
js v6.0 Feb 18, 2019
vendor v6.0 Feb 18, 2019
.gitignore v6.0 Feb 18, 2019
CNAME v6.0 Feb 18, 2019
LICENSE v6.0 Feb 18, 2019 Update README with Netlify Code (#89) (#90) Feb 18, 2019
_config.yml v6.0 Feb 18, 2019
_redirects v6.0 Feb 18, 2019 v6.0 Feb 18, 2019
netlify.toml v6.0 Feb 18, 2019 v6.0 Feb 18, 2019
robots.txt v6.0 Feb 18, 2019
sitemap.xml v6.0 Feb 18, 2019

EVE Trade Finder

A speghetti code SPA that gets the job done. The goal is to eventually move it over to react and rebuild it from the ground up.

Netlify Status


Implements the EVE ESI API to find:

  • the best margins inside your own station.
  • the best trades between stations.
  • the best trades between systems.
  • the best trades between regions.


The following are the base requirements to develop against this codebase. They are split up amongst base package requirements and Jekyll plugins.

Base Packages

Jekyll Plugins

Development and Deployment

The following explain the development guidelines and requirements.


  • To develop locally execute jekyll serve (ensure JEKYLL_ENV=dev -- you should be fine by default)
  • To kick off a Production build:
    • On Mac open any terminal: Run JEKYLL_ENV=production jekyll build
    • On Windows go into CMD Prompt: Run set JEKYLL_ENV=production and then jekyll build
    • The production build must run production build command before committing as minify

Development vs. Production Sites

  • The master branch deploys is the live hosted code
    • Automatically deploys to
    • Only dev can be merged into master so feature branches need to submit pull requests to dev.
  • dev is the development branch where all features will be merged first
    • Automatically deploys to
    • New features added to dev will be tested extensively before merged into master
    • All feature branch pull requests are made to dev