james
/
jtm.dev
1
0
Fork 1
Code Issues Pull Requests Activity
My personal page, now shared with James T. Musselman. https://jtm.dev
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53 Commits
1 Branch
0 Tags
7.6 MiB
CSS 50.2%
HTML 47%
Ruby 2.8%
 
 
 
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Go to file
James T. Martin 09140a4726
Add PGP key to contact info, vendor Gitea icon. 		3 weeks ago
_layouts Add PGP key to contact info, vendor Gitea icon. 3 weeks ago
assets Add PGP key to contact info, vendor Gitea icon. 3 weeks ago
.editorconfig A minimal and attractive redesign. 3 years ago
.gitignore Add PGP key to contact info, vendor Gitea icon. 3 weeks ago
Gemfile A minimal and attractive redesign. 3 years ago
Gemfile.lock Updated site to match current live version. 3 weeks ago
LICENSE.txt Updated site to match current live version. 3 weeks ago
README.md Updated site to match current live version. 3 weeks ago
_config.yml Updated site to match current live version. 3 weeks ago
index.html Add PGP key to contact info, vendor Gitea icon. 3 weeks ago
key.asc Updated site to match current live version. 3 weeks ago
robots.txt Updated site to match current live version. 3 weeks ago

README.md

jtm.dev

This is the source code for my personal website, jtm.dev.

Installation

This project is built using Jekyll, a static site generator.

To install this website, you must first install Jekyll. Next, install all necessary modules with bundle install.

To build the site, run bundle exec jekyll build. To rebuild the site continuously as updates are made, run bundle exec jekyll build --watch. The web root for the website will be _site/. You may point your web server there and the site will work with no additional effort.

To work on the site without installing full web server, use bundle exec jekyll serve.

Code Conventions

All of my code is valid HTML5 and CSS3 according to WHATWG standards

I follow the Google HTML/CSS Style Guide; Google recommends dropping optional tags wherever possible.