insanity54 / grumpydale

Grumpydale.com

This page is intended for developers, webmasters, or site maintainers. This page is a repository of the code that generates grumpydale.com. If you would like to see the website meant for everyone, check out http://grumpydale.com

Build process

Initial setup

After cloning this repository to your workstation, you will need to download all the npm and bower dependencies.

$ npm install
$ bower install

Build step

The Metalsmith templates are be compliled into a website using the metalsmith command line tool, ./node_modules/metalsmith/bin/metalsmith. An easy shortcut to run this tool is to run npm run build (build script defined in package.json)

Upload step

The website is compiled HTML files under ./dist. The contents of dist are then uploaded (ex: ftp) and served by your web services provider (ex: Godaddy.)

You can use FileZilla to upload the files, or a quick and easy method is to use npm run deploy. (sftp dependency)

Favicon generation

Dependencies: Node.js

The master image for the favicon should be 260x260px and have a transparent background. Name it ./src/assets/favicon-lg.png.

Create the cross-platform favicons, outputting them to the ./dist folder:

node ./node_modules/cli-real-favicon/real-favicon.js generate faviconDescription.json faviconData.json ./dist`

Inject the HTML code into the pages

node ./node_modules/cli-real-favicon/real-favicon.js inject faviconData.json ./dist ./dist/*.html

For more info on this process, check out https://realfavicongenerator.net/favicon_result?file_id=p1acmt43uc10hhulg1p5d1l4314cj6

Adding pictures

• Add new code to ./src/partials/gallery.hbs
• Place the pictures inside ./src/assets_img
• npm run build

TODO

• Create pages
  • About the Artist
  • Contact
  • Art
    • Colored Pencil
    • Crayons
• Create templates and partials from index.html
• Create build script
  • Navbar creation
  • Partial injecting
• Fix hamburger menu
• Hide the underline when hovering on images
• Add purple theme

LICENSE

Images are copyright Dale DuRee

Vendor libraries have their own license

All remaining HTML/CSS/JS is MIT license Chris Grimmett

grumpydale's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.