Shortcake (Shortcode UI) chat summary – April 20th, 2015

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Present: @danielbachhuber, @matth_eu

Meeting focused on clearing up some of the remaining issues in the v0.3 milestone.
In v0.4, we’re looking into de-coupling Shortcake from the Media Library experience. If you have opinions on this regard, you should follow along on this issue
Matt has done some exploration of repeatable fields. The crux of the problem is our field templates include the field, and label and description. Fieldmanager and CMB use prototype HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. for repeatable fields. However, before we go about reinventing Fieldmanager, we should reach out to Metadata APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. working group to see how they’re approaching.
Supporting rich text editor for a shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. attribute is a nice idea but has a couple fundamental flaws: 1) HTML can’t easily be stored in shortcode attributes, 2) TinyMCE views gets funky when there’s HTML in the inner_content. The idea needs more technical baking before we can commit it to a milestone.
Goal is to have remaining v0.3 issues into Fusion production by tomorrow morning PT, and then ship Wednesday or Thursday.

Logs: https://wordpress.slack.com/archives/feature-shortcode/p1429556549000347

Next chat: same time and place

#meeting-notes, #shortcode-ui, #shortcodes

Chris Van Patten 12:57 am on April 21, 2015

Just wanted to say thanks for your hard work on this. I’m using it in production for a pretty big regional news publication client and their editorial team loves it (and I love working with it!).
programmin 2:09 pm on April 21, 2015

Sounds good. So would this be a new rewrite of the mce-views coming up in WP 4.3, not 4.2? While it’s nice to have new and better-functioning mce-view, some of us are still waiting on migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. guide to make existing wp-views shortcodes work with the rewrite in 4.2 – http://wordpress.stackexchange.com/questions/184503/wordpress-4-2-mce-views-migration-guide
bfintal 2:26 pm on April 23, 2015

Awesome work Daniel, we’re using Shortcake at the heart of Page Builder Sandwich. I’ll try and help out when I can

Comments are closed.

Welcome!

Communication

Share this: