Typo
Add bootstrap.

I'm using the bootstrap-sass gem since it's now officially part of Bootstrap.
This is generally how you're supposed to use libraries with the asset pipeline:
add a gem which takes care of updating things for you and doing the
integration. I'm not 100% sold on it, exactly, because it relies on people
doing the wrapping rather than importing them directly, but I don't plan on
doing a whole lot of fancy in this app anyway, so it shouldn't be an issue.

The gem instructions don't tell you about adding the file; it took me a bit of
searching to realize that the gem only made the sass files available, rather
than adding bootstrap itself to your project. This makes sense, I guess, if
you want to pick and choose which parts of Bootstrap get used, or to only
use them on part of your sites.
New home page.

Here's a trick that I like in Rails apps: you basically just render the
homepage with `layout: false`, and then shove everything into the single view.

This is an example of where DRY can lead you astray. Yes, I copy and pasted a
bunch of stuff into the view from a layout. Yes, I could, in theory, extract a
common layout and use it for both. No, that would not be worth it. Here's why:

The home page is often just marketing material, and ends up being significantly
different than the rest of the site. Depending on how big your organization is,
it can also end up changing a lot for various reasons, too.

Using the common layout doesn't actually buy you anything, because _the home
page and the rest of your site don't actually have a lot in common_. The
purpose of DRY is to make future change easier. Trying to have this page share
a layout with the rest of the site actually makes future change harder, in my
experience.

Eventually, when I'm ready to launch, this won't be a Bootstrap template, and
will be something real instead.
Bootstrap-ify the layout.

Easy enough. Just the basics.

One thing that's still missing: flash message styling.
Merge pull request #9 from thegcat/patch-1

Typo
Style sign in box
Merge pull request #11 from artisan-tattoo/bootstrap

Bootstrap
add link to root_path on sign in page
Merge pull request #12 from narzero/add_root_link_to_sign_in_page

add link to root_path on sign in page
Empty commit for create artist branch.
Add a link to a new artist from the dashboard.

I like writing tests like these, even though they seem kinda trivial, because
if I do visual refactoring of the HTML/CSS/JS later, I can ensure that I don't
break anything.

I've also moved the `sign_in` helper into a more global scope, as an increasing
number of tests will use it.

Finally, you'll notice that I use `only` in my routes more than most people.
It's true that those will just be a 404 if they're not defined, but I like
being extra explicit here. For example, `rake routes` would show waaaay more
routes than I actually use. Routes are an interface into your application: you
should limit them as much as possible.
Create a new artist.

I looooove `assert_difference`.

Note that this isn't perfect yet: I don't test that it's associated
with the correct shop. But at least I'm making them!

The rest of this is pretty boring, bread and butter kinds of things.
Nothing particularly exciting.
Show the artists on the shop dashboard.

The only really interesting change here is that we make `sign_in` now
return a reference to the shop.
Ensure we associate an artist with a shop

I am not happy about this test, but I'm stumped on how to do
it better. At least I can leave myself a note for if/when this breaks
in the future.
Merge pull request #13 from artisan-tattoo/create_artist

Create a new artist
Add hook for rendering of custom <head> content

This allows layouts and templates to hook into providing their own
<head> element content for the application layout using
CaptureHelper#content_for[1].

[1]: http://api.rubyonrails.org/classes/ActionView/Helpers/CaptureHelper.html#method-i-content_for
Add <link> tag to RSS feed on posts root

This allows browsers and feed readers to auto-detect the RSS feed.

See AssetTagHelper#auto_discovery_link_tag[1].

[1]: http://api.rubyonrails.org/v4.1.0/classes/ActionView/Helpers/AssetTagHelper.html#method-i-auto_discovery_link_tag
Add controller test, assert inclusion of RSS <link>

Per @steveklabnik’s [suggestion][c] to add the previously in-line [pull
request test][prt] to the project.

[c]: https://github.com/artisan-tattoo/artisan_assistant/pull/10#issuecomment-46135726
[prt]: https://gist.github.com/andrewsardone/66f8dacafb0e63feb065
Simplify RSS <link> test w/ assert_select

No need to mess with Nokogiri -- we can just use [assert_select][as].

[as]: http://cl.ly/2Q0Z2s3h3M2s
Replace RSS <link> controller test w/ view test

Per [a suggestion][c] by @steveklabnik. The view test seems to involve a
little more awkward setup (stubbing out @posts and current_shop) and I’m
addmittedly unexperienced with best practices around raisl view testing,
but I suppose a ActionView::TestCase is a little more targeted.

[c]: https://github.com/artisan-tattoo/artisan_assistant/pull/10#commitcomment-6686554