https://github.com/joelvaneenwyk/homepage

Source data for the homepage of Joel Van Eenwyk.
https://github.com/joelvaneenwyk/homepage

homepage html hugo portfolio

Last synced: 2 months ago
JSON representation

Source data for the homepage of Joel Van Eenwyk.

• Host: GitHub
• URL: https://github.com/joelvaneenwyk/homepage
• Owner: joelvaneenwyk
• License: mit
• Created: 2015-05-15T23:35:42.000Z (over 9 years ago)
• Default Branch: develop
• Last Pushed: 2024-07-29T18:49:04.000Z (6 months ago)
• Last Synced: 2024-08-03T22:24:31.423Z (6 months ago)
• Topics: homepage, html, hugo, portfolio
• Language: JavaScript
• Homepage: https://joelvaneenwyk.com
• Size: 269 MB
• Stars: 2
• Watchers: 4
• Forks: 1
• Open Issues: 25
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• jimsghstars - joelvaneenwyk/homepage - Source data for the homepage of Joel Van Eenwyk. (JavaScript)

README

        
# Joel Van Eenwyk

These are the pages and source for [joelvaneenwyk.github.io](https://joelvaneenwyk.github.io/).

[![Code Climate](https://codeclimate.com/github/joelvaneenwyk/homepage/badges/gpa.svg)](https://codeclimate.com/github/joelvaneenwyk/homepage)

This is the source code for the homepage of Joel Van Eenwyk (). Going open source was not my original plan for this, but there are a lot of benefits to doing this. Perhaps my favorite reason being continuous integration (CI) support for free if hosted on a public repository.

The staging branch is also deployed automatically to Heroku at [jvaneenwyk.HerokuApp.com](http://jvaneenwyk.herokuapp.com/).

![Joel Van Eenwyk](static/images/jve_stamp.png)

## Structure

- 📁 `content` - Markdown files and the text content of the site.

- 📁 `static` - Assets not intended to change e.g., stylesheets, images,

  etc.

## Principles and Guidelines

Based on the previous version of this site, there were a lot of learnings. The primary take-away is that the previous site was too complicated. This was especially apparent when trying to go back and revise/update it. This is in part poor documentation but also just relying on unreliable technology. Unfortunately, in the world of the web this is hard to avoid -- it moves at an incredible pace and technology you choose **will** get deprecated and replaced by something that may or may not be production ready.

1. Use only statically typed languages i.e., no JavaScript

2. Everything in the project must be linted

3. CI must be enabled from the start

4. Architecture must be well documented

**Keep it simple.**

## Build and Run

1. [Install Hugo](https://gohugo.io/getting-started/installing/)

   - Recommend using [Scoop](https://scoop.sh/) on Windows

2. Install Heroku CLI

3. From the root, run `heroku git:remote -a jvaneenwyk` so that the app name is assigned

4. Install NodeJS

5. Install Yarn

6. Run `yarn install`

7. Run `yarn start` or just `hugo server`

### Windows Setup

1. Install [Scoop](https://scoop.sh/). Open a PowerShell terminal (version 5.1 or later) and run:

   ```powershell

   # Optional: Needed to run a remote script the first time

   Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

   irm get.scoop.sh | iex

   ```

2. [Install Hugo](https://gohugo.io/getting-started/installing/): `scoop install hugo-extended`

3. Start Hugo server: `hugo server`

## Resources

- 🔒 [jvaneenwyk | Heroku](https://dashboard.heroku.com/apps/jvaneenwyk)