Starting with an updated Gemfile.lock

Starting Issue #72 with some minor updating. No functional change.

RSpec: 453 examples, 0 failures
RuboCop: 126 files inspected, no offenses detected
Ripped out Bootsy again.

RSpec: 453 examples, 0 failures
RuboCop: 126 files inspected, no offenses detected
Added "exploration spec" for RedCarpet.

An exploration spec "kicks the tires" on a third-party code component,
verifying that we know what we think we know about how to use it. This
is a first (working) stab at this one.

RSpec: 455 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 1

Kicked the tires on `: no_intra_emphasis` and `:tables` options.

RSpec: 464 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 2

Now understand `:fenced_code_blocks`, which are important to GFM.

RSpec: 468 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 3

Documented current behaviour of/defaults for `:autolink` option.

RSpec: 471 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 4

Documented current behaviour of/defaults for
`:disable_indented_code_blocks` option.

RSpec: 474 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 5

Documented current behaviour of/defaults for
`:strikethrough` option.

RSpec: 477 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 6

The `:lax_spacing` option is documented but has no apparent effect; we
get the code block either way. Pffft.

Now using the master-branch version of `redcarpet` because there have
been so many commits since the last formal release. Changing this had
no effect on `:lax_spacing`.

RSpec: 479 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 7

Documented current behaviour of/defaults for
`:space_after_headers` option.

RSpec: 482 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 8

Documented current behaviour of/defaults for
`:superscript` option.

RSpec: 486 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options, pt 9

Documented current behaviour of/defaults for
`:underline` option.

RSpec: 489 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options pt 10

Documented current behaviour of/defaults for
`: highlight ` option.

RSpec: 492 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options pt 11

The `quote` option, like the `:lax_spacing` option, is documented but
has no apparent effect; we
get the `<q> tag pair either way. Pffft.

This next (and last-in-the-arc) commit is likely to be a bit more
detailed: footnotes.

RSpec: 494 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
Verifying understanding of RedCarpet options pt 12

Documented current behaviour of/defaults for
`: highlight ` option.

Note that this has a not-entirely-intuitive syntax that makes it
trivially easy to break the markup such that the feature appears not to
work. Omitting *any* of the following will break parsing:

* the ^ before the footnote number in either the reference or
definition;
* the colon after the closing bracket in the footnote definition (see
line 573); or
* the newline at the end of the footnote definition;
* *multiple* blank lines (newlines) before the footnote definition.

Anybody that wants to use this *must* supply a preview; it's simply too
easy to screw it up.

RSpec: 492 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
PostDataDecorator supports Markdown body content.

Still need to convert feature specs; they still work because valid HTML
is by definition valid Markdown. :relieved:

Also includes new minor refactoring-type editing of other files.

RSpec: 497 examples, 0 failures
RuboCop: 127 files inspected, no offenses detected
More Markdown-related Post body changes.

* New post helper for feature specs now generates a post body with an
embedded inline element (emphasised text); this helps us prove that we
can in fact handle embedded Markdown;
* New "Member can publish an article and view it on the landing page"
spec proves that that "embedded inline element" is correctly rendered;
* Minor cleanup to PostDataDecorator spec;
* PostDataDecorator's ImageBodyBuilder spec strips a
meaningless-in-context newline that's always added to generated content
by RedCarpet;
* PostDataDecorator's ImageBodyBuilder code converts the passed-in body
markup to HTML (from Markdown/HTML/who cares?);
* New PostDataDecorator::SupportClasses::ContentConverter class to do
that conversion;
* Ripping the Markdown-aware stuff out of the main PostDataDecorator
class, now that we've the shiny new ContentConverter support class.

RSpec: 498 examples, 0 failures
RuboCop: 129 files inspected, no offenses detected
New UserDataDecorator class specced and coded.

New `UserDataDecorator#build_profile` method is analogous to
`PostDataDecorator#build_body` in that it implements rendering of
Markdown markup as HTML.

RSpec: 507 examples, 0 failures
RuboCop: 131 files inspected, no offenses detected
Finishing up user bio/profile as rich content.

* First, see the relatively simple change made to the FactoryGirl
`:user_datum` factory in `spec/factories/user_data.rb`; the `profile`
field now has a Markdown-italicised word in it. Simple, but sufficient
to help show that Markdown-persisted content is rendered properly.
* Next, look at the Users :show template in
`app/views/users/show.slim`. Besides deleting some previously
commented-out crap, the call to the `#profile_bio_panel` helper
function passes in `user.build_profile` rather than the previous
`user.profile`. This translates the Markdown content in the `:profile`
attribute into HTML and passes it to the helper, which expects HTML.
* The spec for `UserDataDecorator` should be pretty self-explanatory;
kick the tires on the golden path for the `:build_profile` method.
* Finally, the updated
`spec/features/member_can_view_own_profile_page_spec.rb` verifies that
the HTML-rendered profile content is properly included in the profile
page.

Pinging Issue #72.

RSpec: 507 examples, 0 failures
RuboCop: 131 files inspected, no offenses detected
Merge pull request #73 from jdickey/issue-72

Fixes Issue #72, but see #74. Changing rich-content persistence to Markdown from HTML.