Add missing app_title variable
Upgrade Bootstrap to 3.3
Better slug unique warning for Documents

As editors may be editing documents with the same title we needed to
improve the functionality of this warning. This commit changes the
warning text to an alert to be more visible, disables the Publish button
if it is not unique and only makes the uniqueness check happen if the
document isn't currently Published. This means that you can still
Publish already published documents.
Better slug unique warning for Manuals

Same process as Specialist Documents. Disable the publish button if
there is a slug clash, move the warning to a banner and change the
slug check to only be displayed on the draft Manual.
This method is a duplicate of an attr_reader
Add other formatters to wiring

After some moving around of these files, they weren't in the autoload
path anymore. This commit fixes that.
Merge pull request #338 from alphagov/upgrade-bootstrap

Upgrade Bootstrap to 3.3
Use the correct published_at date

When publishing, we first update the document to say that it is
'published', then we export it to the content api. Because by the
time the exporter calls the published_edition after the document has
been updated to published, this returns the latest_edition instead.

Instead we must find the last major edition and use its updated_at
to retain the published at date across minor updates.
Merge pull request #346 from alphagov/fix-formatter-requires

Add other formatters to wiring
Merge pull request #344 from alphagov/better-slug-unique

Better slug unique warning
Merge pull request #347 from alphagov/feature/minor-updates-dont-update-published-at

Minor updates dont update published at mk2
Sort by relevant date before bulk publishing

DSU: first_published_at
Medical Safety Alert: issued_date
RAIB, MAIB: date_of_occurrence
Merge pull request #348 from alphagov/sort-by-chosen-date-on-bulk-publish

Sort by relevant date before bulk publishing
Rename update timestamp to public

With the work to create updates from publication logs we mistakingly
renamed this. This commit corrects it to public_timestamp like other
document formats.
Reverting published_date changes

Our work regarding only setting published_at did not work as expected.
This commit reverts those changes in order for us to start with a clean slate
when setting the published_at date for SpecialistDocuments
Explain major and minor for publishing

As Users now have change notes, we should probably explain what type of
change it is and what impact publishing will have.

Ticket:
https://trello.com/c/mUPdaenr/426-minor-major-edits-confirmation-on-publish-2
Merge pull request #349 from alphagov/rename-update-timestamp-to-public

Rename update timestamp to public
Merge pull request #350 from alphagov/major-minor-explanation

Explain major and minor for publishing
Store public_updated_at for sorting finders and frontend updated_at

As the repository only pulls out the last 2 document editions there is no
garauntee that we will always have pulled out a document edition that is a
major update. Instead we will create a field which stores the date of publish
for the last major update. This is persisted across editions and exported to
rummager and content-api as the date which defines when a document was
last updated from the front end user's perpective.
Fix Publication Log Change History migration

Previous version of this migration returned SpecialistDocumentEditions
with empty array change notes history. This commit fixes the query to
only return editions with a change note history with something in it and
also adds a condition to make sure that the object pulled from the array
isn't nil.