Tag Archives: introduction

pantheon.io and wordpress: intro to a potential three-parter

disclaimer: i started writing this in december and then realized it was a lot more information than i thought (mo’ files = mo’ problems). so i split the info into three categories, but i haven’t written the latter two yet. the first is mostly ready so should be out soon. skip to part one


for the past three months, i’ve been using pantheon.io for my development process making a relatively small but almost entirely custom wordpress build. pantheon specializes in hosting and managing wordpress and drupal sites, and for me was mostly a good experience. for some quick tl;dr:


  • Git integration and insta-repo — push changes right from command line or your preferred Git client
  • handles all of your server needs and maintenance
  • somehow free for the first 15 sites
  • relatively easy to initialize and go between dev and testing environments (with a few caveats*)
  • sFTP options
  • one-click backups per-environment


  • setting up locally is a bit of a pain and docs are outdated
  • if you are migrating a large site, gear up your command line skills and pat yourself on the back for good luck
  • exporting a large site for the first time is similarly awkward
  • not really sure what’s happening with the database unless you export the whole thing and look
  • the git/sftp toggle makes updating wordpress & plugins a pain
  • if you’re not sticking with pantheon for the entire dev to live process, it can get a little…awkward, shall we say.

in the upcoming articles, i will (hopefully) outline:

  1. starting from scratch on or migrating a site to pantheon
  2. developing with pantheon
  3. exporting a site from pantheon

note that this article assumes a basic understanding of source control (specifically Git) and wordpress, and that i develop on a macbook pro so most of this will be with os x experience.

*stay tuned!

thoughts from today in responsive web design

i’m in class today, so a lot of these helpful hints have to be attributed to my professor, Andrew Smyk.

today we’re talking about how to get your website noticed and up to responsive web design standards.  my professor purposefully broke his website and made his code terrible as a teaching tool. a pretty effective tool, at that. it’s like a scavenger hunt for bad code!

anyway, here are some dos and don’ts for all of your beautiful webpages:

  • DO: a favicon. let me repeat that. a favicon. apparently this will increase clickability in the browser by 50%. you know how when you have a bunch of tabs open you’re more likely to go back to the tabs with pretty pictures instead of a nondescript blank page icon? yeah. that.

Continue reading thoughts from today in responsive web design

the start.

hello, future readers! in an attempt to set up a working and customized wordpress site (for practice, of course), I thought, why not just make a real blog out of it? so here we are.

I’m not sure how much this will be updated — I was an avid writer in high school but have since found it hard to write about my own opinions (having to cite every reasoning/sentence you ever write for lab reports over four years will do that to you, apparently. schience). maybe this will spark my writing interest, who knows.

I’m also a bit of a stickler for spelling and grammar so if you see any unintended typos please tell me — although ironically I’m not too bothered by capitalization, as you may have noticed. sometimes fluid rules are good for you, or whatever. right?

anyway, (and congrats if you’ve read this far), i hope you find something enlightening/fun/at least a tad interesting while reading. let the writing begin! (i think. it’s up to future me for that one.)