Skip to content
This repository has been archived by the owner on Mar 14, 2021. It is now read-only.

vtange/wintersmith-practice

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

wintersmith-practice

Practiced wercker deployment of Wintersmith builds

Tech

Wercker, Wintersmith, Jade, Markdown

Niceties

Markdown Content, Automated gh-pages.

Takeaways

  • Wintersmith gives a template from which you can easily make a blog with .md files.
  • install with npm install -g wintersmith
  • start with wintersmith new [project name]
  • wintersmith preview from master branch to see full site pre-build.
  • The wercker deploy at gh-pages works by running wintersmith build and pushing the /build directory (Which contains the static HTML and associated CSS) to the gh-pages branch
  • wercker depends on creating and linking an 'app' on their site to a repo such as this one. Whenever master branch updates, wercker will run the wercker.yml file, much like a Grunt or Gulp process
    • wercker 'steps' are like npm modules in which you have to define one that either exists in marketplace or author your own.

Cons

  • .yml files cannot have tabs.
  • wercker build messes up with pathing for CSS files, etc. searches vtange.github.io/main.css instead of vtange.github.io/repo-name/main.css
  • too blog-like. generates pages out of .jade and markdown(.md) files. If you're going to make mulitple unique microsites, might as well do it via Express.

Releases

No releases published

Packages

No packages published