package_v0.2.3_v3.1.1

@frontkom/gutenberg v0.2.3

• Updated to Wordpress/gutenberg 3.1.1
• Removed addCategories and removeCategories actions from core/blocksstore (setCategories can handle boths)
• Added attributes to Section Block (maxWidth, backgroundColor, hasImage, image url, hasParallax, dimRatio and data attributes)

package_v0.2.0_v3.1.0

@frontkom/gutenberg v0.2.0

• Gutenberg modules are now availabe in @frontkom/gutenberg package. Check docs to see how to initialize the editor.
• Most of window.customGutenberg props were removed (blocks and categories props were removed and now are set in Storypage module).

StoryPage module

The StoryPage module was added to @frontkom/gutenberg and contains:

• blocks: Post, Row and Section
• and components: PostPanel

which could be registered and added to the editor.

Publish, Save and Autosave

Publish, Save and Autosave flags were moved from postType object to editor settingsand are called by canPublish, canSave and canAutosave

Sidebar plugins

• Check docs to see how to add PostPanel to Document tab

package_v0.2.2_v3.1.0

@frontkom/gutenberg v0.2.2

• Added type attribute to Post Block;
• Added Dependencies section to README.md.

package_v0.2.1_v3.1.0

@frontkom/gutenberg v0.2.1

• Post block was updated (some attributes were removed and some default value were changed)
• Improved ADD_CATEGORIES action (in order to add categories at the end or at the beginning of the array)
• Made possible to set Section block as default block
• Fixed package webpack config (added missing style vars)

package_v0.1.3_v3.0.1

@frontkom/gutenberg

• Removed custom Extra tab. Please check Plugins and edit-post docs to know how to add extra sidebars
• The package exports all Gutenberg modules now. Please check the updated Usage section.

package_v0.1.2_v3.0.1

@frontkom/gutenberg

• The document property was removed from postType object. That means Document tab display can't be controlled anymore.
• Fix: Removed default value for Extra tab PostTypeSupportsCheck

package_v0.1.1_v3.0.1

@frontkom/gutenberg

• The initializeEditor method was changed, please check documentation
• New event added to customGutenberg.events object: 'REMOVE_BLOCKS'
• data attributes were added to CoverImage block
• Registering Custom Blocks are available now

package_v0.1.0_v3.0.0

@frontkom/gutenberg

• Using Gutenberg 3.0.0

Please check the last release notes.

package_v0.0.22

• Moved Gutenberg package to packages/gutenberg dir and changed dist folder name to build. Also a new style file is required (theme.css):

import '@frontkom/gutenberg/build/css/core-blocks/style.css';
import '@frontkom/gutenberg/build/css/core-blocks/edit-blocks.css';
import '@frontkom/gutenberg/build/css/core-blocks/theme.css';
import '@frontkom/gutenberg/build/css/style.css';

• On initializeEditor( 'editor', post, settings ), now it is expected:

  • The id prop in postobject (ex: id: 123)
  • The autosaveInterval prop in settings object (ex: autosaveInterval: 10)

• The new Gutenberg Autosave feature requires a new api-request request:

  • PUT /wp/v2/[postType]/[id]/autosaves, which returns post or page object (see to POST post/page response)
  • To disable Autosave, add autosaveable: false to type object on GET types response

package_v0.0.21_v2.9.2

Extra tab and Inserter menu block

• Now is possible to add an extra empty tab to the editor's sidebar, adding extras: true prop to type.supports object;

• As Inserter Menu tabs were replaced by panels and also its customGutenberg configuration: set blocks instead tabs property in customGutenberg object.