release-v3.2.1

June 2018. ConfigObject: Store, edit and read global data - Improved Labrador-menu - Improved admin-pages

  • Feeds. Labrador ships with an feed-editor. The editor is available at the admin-pages and lets users add feeds without any developers modifying the view.

  • Editable config-data and content. Config-data allows editors and users to modify the Labrador-installations themselves instead of relying on a developer to modify files in the view. You can add admin-tools for storing any config-data or content-data.

  • Fallback-site. If you have several sites on one Labrador-installation that shares site-config you can specify a fallback-site using “lab_fallback_site”. This allows you to skip duplicate config for sites that share functionality and styling.

  • Invisible menu-items. If you need to register a hotkey when user hovers a contentbox you can add a menu-item without any markup, only the hotkey.

  • Improved ColorPicker. You can use the buildt-in color-picker to set any metadata on a structure. It’s suitable for data where user should pick a value from an array of values.

  • Bug-fix: Bodytext-editing. Some dom-attributes from Labrador, like “droppable” persisted throug to the published article. This is now removed.

  • Improved image-editing. When zooming an image the center point is now where the cursor is placed. This increases precision and allows for gestures like pinching using a touch device.

  • Save styles. When editing article-teasers you can let users save all visual attributes of a contentbox and apply it to others. This makes it more easy to use very specific and strict styling on a page. The styles are currently stored on the page node and is only available on current page.

  • Version-string for view. You can display a version-string for the view to users and developers. See documentation “Add version-file to view” in the editor for more info.

  • Cache-busting. All scripts and css-files in the editor will now automatically update in the browser for any new CMS-commit. See “view.cachebuster” in documentation “Access data in template” for example on how to use it in your own templates.

  • Edit on touch-devices. Labrador supports simple editing on touch-devices. See documentation “Edit pages from a touch-device” in Labrador for more info.

  • The Labrador menu now floats on top of the page and is always visible. A quick look will give users an idea of which page is beeing edited and page-status. Users can open and close the menu as before using the keyboard-shortcut “,” (comma) or click the hamburger button on the right hand side. The open menu can be expanded to display more items.

release-v3.2.0

April 2018. Viewport-independent editing

  • Moved several menu-adapters from view to CMS. This allows Publish Lab to maintain and update menus with little variations from one customer to another: media.images, media.image_upload, media.slideshow, media.this_page

  • Contextual menus can display status based on the content it belongs to.

  • Viewport-specific metadata. Labrador can store viewport-specific structure-metadata and make it available for the template. This makes it easy for you to set metadata that can be overridden by secondary viewports.

  • New view-methods: "strip_tags", "trim", "viewport_data"

  • Edit, drag and drop between any viewport

  • Fully functional "mobile first"-editing

release-v3.1.2

Desember 2017. New features required for site khrono.no

  • Text editing: All inline style is now stored per viewport. Use CSS to inherit inline style across devices.

  • Increased max_image_upload_size to 30MB

  • Feed-filtering, remove article-duplicates

  • Bugfix, added cache-channels to tag-requests from the API

  • New droppable-option: "prependChild". Will add the new content as the first sibling

  • Option to limit number of children drawn by data

  • A warning is displayed when unpublishing content

  • Option to update metadata on existing structures using “structureTemplates”

  • Menus for text-tools can reflect state of selected text

  • Default resource_map is read from "sites.default.resource_map"

  • Templates can remove whitespace with "view.trim": {{ #view.trim }} classNames with lots of white-space {{ /view.trim }}

  • Easier to specify viewport-specific data

  • Buildt in support for full-width images

  • Structure-data supports bindings like content-data

  • New tool: ColorPicker. Adds text-color, background-color, gradients and custom colors based on user-config

  • New tool: TeasersEditor. Simplifies setting teaser-data and front-crops for article-pages. Support rich teaser-text

  • Add params for article api to return facet/group by counts (t.ex article count per month)

release-v3.1.1

September 2017. Personalized content, improvements and bug-fixes

  • Personalized content

    https://github.com/publishlab/view-resources/tree/feat-personalized-content

  • Bugfix for editing captions for slideshows

  • Bugfix for editing tags on automatic front-pages

  • LabFrontInspector (UrlAnalyzer): admin-GUI in CMS

  • File Upload via Admin

  • App-menu improvement: Display number of hidden menus. May be customized

  • Reduce effect of 404-requests on labfront

  • Bugfix: Removed global vars

  • Dashboard: Option to sort article-lists on publish-date, modification-date or created-date

  • Pasting of rich text: The editor removes rich content. Config can specify what to allow

  • Dashboard: Option for displaying larger images and removal of subtitles

  • Edit caption on original images

  • Bugfix: Store the field "termMode" as a boolean value

release-v3.1.0

August 2017. Split-testing, Article-collections and more

  • Nodecollection / article-collection

  • A/B-testing, spilt-testing

  • Any viewport can be main viewport

  • Page can override config by data

  • Pusher-plugin supply live-updates of dashboards

  • The Fragment-API can now be used on automatic front-pages also

  • Preloaded urls may now use header-data