Skip to content
trunk
Switch branches/tags
Code

Latest commit

* Created an EmbedPreview component to house the caption.

* Disabled the placeholder mode temporarily until the linking is enabled.

* added the react-native-web-view package.

* linked react-native-web-view to ios

* integrated react-native-web-view with android

* initial integration of WebView into the embed-preview component.

* added project configurations for react-native-webview android

* Add sandbox component native version

* Use webview to preview embed block

* Update aspect ratio calculation in sandbox component

* Add native styles to sandbox component

* Open embed content in external browser

* Add comment to sandbox webview

* Update react-native-webview package to wp-fork

* Bump react-native-webview version

* Bump react-native-webview version

* Use provider url as base url for embed webview

* Add forceRender param to trySandbox

* Handle case of setting empty URL after preview

* Enable embed preview interaction when selected

* Add max allowed requests to embed preview

* Prevent navigation in embed preview on Android

* Recreate WebView in Android on orientation change

* Disable embed preview interaction

* Remove unused clientId prop from embed web version

* Enable inline preview only in dev mode

* Remove URL from embed block internal state

I noticed that for the mobile version we don't really need to keep the URL in the internal state, as we were only modifying it once it changed, and that's already being handled with the url block's attribute.

* Use memo in embed preview component

* Use memo in sandbox component

* Rename iframe html to content html and update logic

* Bump react-native-webview package

* Add align styles to embed preview

* Add embed aspect ratio styles to sandbox static html

* Remove width calculation from sandbox

We really only need to calculate the height as the width should fit the block's size.

* Add webview content style in sandbox

* Disable scroll and zoom features in sandbox

* Use html for rendering embed images

Previously embed images were rendering the thumbnail instead of the original content.

* Remove unused embed style fallbacks

* Revert "Use html for rendering embed images"

This reverts commit 34f1636.

* Add comment to sandbox styles

It references the styles from the web version that have been adapted for native version.

Co-authored-by: Joel Dean <jdeanjj1000@gmail.com>
6e232d9

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time

Gutenberg

End-to-End Tests Static Analysis (Linting, License, Type checks...) Unit Tests Create Block React Native E2E Tests (iOS) React Native E2E Tests (Android)

lerna

Screenshot of the Gutenberg Editor, editing a post in WordPress

Welcome to the development hub for the WordPress Gutenberg project!

"Gutenberg" is a codename for a whole new paradigm in WordPress site building and publishing, that aims to revolutionize the entire publishing experience as much as Gutenberg did the printed word. Right now, the project is in the second phase of a four-phase process that will touch every piece of WordPress -- Editing, Customization (which includes Full Site Editing, Block Patterns, Block Directory and Block based themes), Collaboration, and Multilingual -- and is focused on a new editing experience, the block editor.

The block editor introduces a modular approach to pages and posts: each piece of content in the editor, from a paragraph to an image gallery to a headline, is its own block. And just like physical blocks, WordPress blocks can be added, arranged, and rearranged, allowing WordPress users to create media-rich pages in a visually intuitive way -- and without work-arounds like shortcodes or custom HTML.

The block editor first became available in December 2018, and we're still hard at work refining the experience, creating more and better blocks, and laying the groundwork for the next three phases of work. The Gutenberg plugin gives you the latest version of the block editor so you can join us in testing bleeding-edge features, start playing with blocks, and maybe get inspired to build your own.

Getting Started

Get hands on: check out the block editor live demo to play with a test instance of the editor.

Using Gutenberg

Developing for Gutenberg

Extending and customizing is at the heart of the WordPress platform, this is no different for the Gutenberg project. The editor and future products can be extended by third-party developers using plugins.

Review the Create a Block tutorial for the fastest way to get started extending the block editor. See the Developer Documentation for extensive tutorials, documentation, and API references.

Contribute to Gutenberg

Gutenberg is an open-source project and welcomes all contributors from code to design, from documentation to triage. The project is built by many contributors and volunteers and we'd love your help building it.

See the Contributors Handbook for all the details on how you can contribute. See CONTRIBUTING.md for the contributing guidelines.

As with all WordPress projects, we want to ensure a welcoming environment for everyone. With that in mind, all contributors are expected to follow our Code of Conduct.

Get Involved

You can join us in the #core-editor channel in Slack, see the WordPress Slack page for signup information; it is free to join.

Weekly meetings The Editor Team meets weekly on Wednesdays at 14:00 UTC in Slack. If you can not join the meeting, agenda and notes are posted to the Make WordPress Blog.

License

WordPress is free software, and is released under the terms of the GNU General Public License version 2 or (at your option) any later version. See LICENSE.md for complete license.



Code is Poetry.