Version 2.0.0

First public release. 🎂🎉

Version 1.0.21 Beta

Changed

• #535: open linkable fields in new window

Fixed

• #638: fix issues when saving existing Reference fields

Version 1.0.20 Beta

Changed

• minor fixes in preparation for 2.0.0 release.

Version 1.0.19 Beta

Added

• add globals object to configuration file.

Version 1.0.18 Beta

Fixed

• gracefully handle empty apis configuration block

Version 1.0.17 Beta

Added

• #543: ensure DropArea respects MIME type validation

Changed

• #629: escape HTML when creating code block
• #630: make contains the default operator when creating new filter

Fixed

• #419: recover from remote API validation errors
• #527: gracefully handle API authentication errors
• #623: show notification after deleting items on media list view

Version 1.0.16 Beta

Fixed

• ensure images are loaded from CDN when a cdn block exists in the configuration

Version 1.0.15 Beta

Added

• #573: add media list view
• #577: add media edit view
• #592: add support for inline images in rich editor
• #601: add Color field
• #605: add workspace directory
• #614: display version number in menu

Changed

• #571: improved functionality of Link control in rich editor
• #600: rebuild filters
• #615: display "Document not found" message for uncomposed references

Fixed

• #412: stop unsaved changes from leaking to different documents
• #564: fix issue with rich editor and multi-language documents
• #593: fix issue with changes to fields not being persisted
• #595: fix issue with language dropdown causing an error in document edit view
• #596: fix issue with save options causing an error in document edit view
• #603: stop notifications from obstructing full width of the viewport

Version 1.0.14 Beta

Added

"Linkable" fields

Linkable fields allow you to use the value of a field to create links to external resources in the Publish interface.

An example use case for this is a Twitter username. By specifying a display.link property, Publish creates a full link for display, using the value of the field in place of the {value} placeholder.

Example API schema

"twitter": {
  "type": "String",
  "label": "Twitter",
  "publish": {
    "section": "Details",
    "display": {
      "edit": true,
      "list": true,
      "link": "https://twitter.com/{value}"
    }
  }
}

If the value of your field is already a fully formed URL, set the link property to true to have Publish create a clickable link:

"twitter": {
  "type": "String",
  "label": "Twitter",
  "publish": {
    "section": "Details",
    "display": {
      "edit": true,
      "list": true,
      "link": true
    }
  }
}

Changed

• #559: This PR addresses a small issue if you set a Reference field or Media field as the first displayed field in your API schema you are unable to click through from the list view (both those fields override the link).
• #562: adds a basic fullscreen mode for the rich editor
• #565: use field name as label in columns when no label specified
• #568: disable autocomplete in input elements

Version 1.0.13 Beta

In this release, Publish gets a UI refresh. Additional changes linked below.

#489: Reference field no longer editable when set to readonly
#511: Refactor SSL, resolves installation issue using Node.js 10
#526: Support multiple referenced images
#538: Render first image only in list view when a field contains multiple images
#544: Fix issue with fields with dropdown options failing to save
#545: Fix pagination links when sorting
#554: Media field added to replace subType "Image". Use "subType": "Media" in field configurations
#555: Image fields use CDN for preview if configured