v0.14.0

Fixed

• Changing which support package a published deck recommends now reaches the
  client. The deck froze what the client sees when it was published, to stop a
  repriced package changing a quote already sent — but it froze the choice as
  well, so a new override, a change of hours or a different comparison list
  stopped at the editor. Prices stay frozen; the choice does not.

Changed

• The client logo is off the cover and off the What we do slide. The client
  knows whose deck it is; it still signs off the last slide.
• A service slide's description runs the full width of its column now, level
  with the heading above it, instead of wrapping a third of the way across.
• The second estimate figure is labelled 'Post launch' rather than 'Ongoing
  estimate', matching what the slide it belongs to is called.
• Every estimate total says 'hours' after the number, rather than leaving the
  client to guess the unit.
• The estimate slide shows both figures — what the build costs and what
  carries on afterwards — where the top right used to repeat the slide's own
  title. A deck with no post-launch work shows only the one.
• The support packages table shows each package's included hours in the
  Allowance column, so they can be read down the page instead of only in the
  small print under each name.
• The line under the hosting price saying roughly how many upkeep hours it
  covers is gone. That figure is ours, not the client's.

v0.12.0

Changed

• The deck editor picks up the latest shared admin design. The save bar is
  pinned to the bottom of the window instead of drifting up the page on a short
  screen, and toggles now sit to the right of the setting they switch, lined up
  down the edge. A switch that cannot be used says so rather than highlighting
  when you drag across it.

v0.7.1

Added

• An archived deck can now be deleted. The action shows on archived decks only,
  asks before it acts, and removes the deck, its content and its client link for
  good. A draft or a published deck has to be archived first.

v0.7.0

Added

• Hosting is its own tab in the editor and its own page in the deck: the
  platform, the upkeep behind it — servers, updates, databases and mail — and
  what it costs a month. It carries a price in each of the four currencies, set
  once in Settings and copied onto every new deck. The page stands whether or not
  a fee has been quoted yet; the price appears once it has.
• A Reviews and reverts phase, before QA and testing, so a client sees the
  finished work and asks for changes before anything is tested.
• The content library now arrives already written, from the standard BlueWorx
  deck: every slide's wording, and every line item on both estimates. It updates
  itself on a plugin update, and leaves anything you have edited exactly as it is.

Changed

• Every slide showing hours or a price now says outright that the figures are
  estimates and are subject to change.
• The timeline is worked out from the estimates rather than typed. A phase lasts
  as long as its hours say it lasts, at four hours of work a day, phases run in
  the order the estimates declare, and a phase appears to the client only when its
  work does. Nothing on the tab is editable, and the calendar-date view is gone —
  a proposal does not know when the project starts.
• The timeline is split at launch, on the client deck and in the editor:
  Development phase, then Post-launch. A project has an end and a retainer does
  not, and one unbroken chart read as the same commitment. Each counts its own
  weeks from week one, and in the editor they are tabs — one plan on screen at a
  time. Launch closes the development phase rather than opening the retainer.
• Disabled dropdowns no longer draw a row of WordPress chevrons across the field.
• Which phase a piece of work belongs to is now set in the content library and
  shown, read-only, on a deck. It decides where the work lands on the timeline, so
  a deck moving one would move its own schedule.
• Project management is now post-launch work rather than project work.
• Competitor research, content and editing, and the accessibility pass have been
  dropped from the project estimate; performance optimisation and SEO from the
  post-launch estimate. Feature improvements is now Post-launch updates.
• Text boxes in wp-admin wear the design system's rounded corner and border again,
  instead of WordPress's own square 2px one.

v0.5.0

Changed

• The content library is now the only place a deck's content comes from. Every
  new deck arrives as a copy of the whole library — every section and every line
  item, all switched on — and from then on the copy is that deck's own. Editing a
  library entry changes what the next deck starts with and leaves existing decks
  untouched. The separate hardcoded retainer set is gone, so there is no second
  list to disagree with the first.
• Creating a deck is one click. The starting-point screen has gone, along with the
  choice between a retainer deck and a blank one: "Create new deck" makes the deck
  and opens it, and the client, title and currency are filled in on the deck
  itself.
• A deck's sections, its two estimates and its timeline are fixed lists. Nothing
  can be added, removed, duplicated or reordered, and the library pickers have
  gone with them. Every section presents in the same order every time. What each
  one says, and whether the client sees it, are still per deck.
• The content library can be browsed, edited and deleted from, but not added to.
  A new entry is a change to what the business offers, so it is made in code.

Fixed

• Dropdowns drew two arrows — WordPress puts its own chevron on every select in
  wp-admin, and it was landing beside the design system's. They also wore
  WordPress's height, border and corners instead of ours.
• Screens and panels ended flush against the bottom of the window, with no
  breathing room under the last thing on them.
• The actions column on every table had no heading, because it shared the class
  that fades row actions in on hover. It now says "Actions", and a table too wide
  for its card scrolls inside the card instead of spilling past it.

v0.4.1

Fixed

• Four icons were missing from the design system, so they drew nothing at all:
  the link on the “Live client links” tile, the two content library and
  package empty states, and the device buttons on the deck preview.

Changed

• The Deck Builder menu item carries a BlueWorx icon rather than a WordPress
  one. It does not brighten on hover the way WordPress's own icons do —
  WordPress paints it as a background image, which cannot take a colour.

v0.4.0

Added

• A BlueWorx: Sales Agent role. It can do everything in the deck builder
  and nothing else on the site — no posts, pages, comments, users, settings
  or plugins. Pick it when adding a user.

Changed

• The deck builder is behind a permission of its own rather than the site's
  settings permission. Administrators and sales agents have it; nobody else
  does, including editors.
• Decks, packages, case studies and library entries are behind the same
  permission, so WordPress's own checks agree with the plugin's screens.

Client links are unaffected. A published deck stays open to anyone with the
link, with no WordPress account needed.

Fixed

• Archiving or restoring took the record id on trust. It checks the record is
  a deck first, and says so when it is not.

v0.3.0

Added

• Build a deck from things you have written before: tick a section or a line
  item from the content library, save, and it is copied into the deck. The
  copy is the deck's own, so editing it there leaves the library alone.
• Keep a line item for next time. Turn on "Save to library" on any estimate
  row and saving files it in the library, without its internal note.
• The content library now holds line items as well as sections, and a fresh
  install starts with six of the ones that turn up on most quotes.
• See the client deck without leaving the builder: the share tab frames the
  real page at desktop, tablet and phone widths. A deck can be checked this
  way before it is ever published.

Changed

• The plugin is listed in WordPress as "BlueWorx Labs | Deck Builder".
• The two "in package" figures above the tabs are now one, because that is
  the single number the package recommendation is worked out from.