Gutenberg

Disgrifiad

Mae Gutenberg yn fwy na golygydd. Er mai golygydd yw’r ffocws ar hyn o bryd, bydd y prosiect yn effeithio ar y profiad cyhoeddi cyfan yn y pen draw, gan gynnwys cyfaddasu (y canolbwynt nesaf).

Darganfod mwy am y prosiect .

Ffocws golygu

Bydd y golygydd yn creu profiad newydd o dudalen ac ôl-adeiladu sy’n gwneud ysgrifennu cofnodion cyfoethog yn hawdd, ac mae ganddi "flociau" i’w gwneud yn hawdd i wneud yr hyn y gallai ar hyn o bryd gymryd codau byr, HTML cyfaddas, neu ddarganfod mewnblannu "mystery meat". – Matt Mullenweg

Un peth sy’n gosod WordPress ar wahân i systemau eraill yw ei fod yn caniatáu i chi greu cynllun cofnod mor gyfoethog fel y gallwch chi ei ddychmygu – ond dim ond os ydych chi’n gyfarwydd â HTML a CSS ac yn adeiladu’ch thema cyfaddas eich hun. Drwy feddwl am y golygydd fel teclyn i’ch galluogi i ysgrifennu cofnodion cyfoethog a chreu gosodiadau hardd, gallwn drawsnewid WordPress i fod yn rhywbeth mae defnyddwyr wrth eu boddau gyda WordPress, yn hytrach na rhywbeth maen nhw’n ei ddewis oherwydd dyma mae pawb arall yn ei ddefnyddio.

Mae Gutenberg yn edrych ar y golygydd fel mwy na maes cynnwys, gan ail-edrych ar gynllun sydd heb ei newid yn sylfaenol ers bron i ddegawd. Mae hyn yn ein galluogi i ddylunio profiad golygu modern a datblygu sylfaen ar gyfer pethau i ddod.

Dyma pam yr ydym yn edrych ar y sgrin golygu gyfan, yn hytrach na dim ond y maes cynnwys:

  1. Mae’r bloc yn uno rhyngwynebau lluosog. Os byddwn yn ychwanegu hynny ar ben y rhyngwyneb presennol, byddai’n ychwanegu cymhlethdod, yn hytrach na’i ddileu.
  2. Drwy ail-edrych ar y rhyngwyneb, gallwn foderneiddio’r profiad ysgrifennu, golygu a chyhoeddi, gyda defnyddioldeb a symlrwydd mewn golwg, sy’n fanteisiol ar gyfer defnyddwyr newydd ac achlysurol.
  3. Pan fydd rhyngwyneb bloc unigol yn cymryd rhan ganolog, mae’n cynnig llwybr clir i ddatblygwyr greu blociau premiwm, sy’n well na codau byr a theclynnau.
  4. Mae ystyried y rhyngwyneb cyfan yn gosod sylfaen gadarn ar gyfer y ffocws nesaf sef, cyfaddasu gwefannau llawn.
  5. Mae edrych ar y sgrîn golygydd lawn hefyd yn rhoi’r cyfle i ni foderneiddio’r sylfaen yn sylweddol, a chymryd camau tuag at ddyfodol mwy hylifol a grym JavaScript sy’n cymryd mantais llawn o API REST WordPress.

Blociau

Blociau yw esblygiad unedig yr hyn sydd bellach yn cael ei gwmpasu, mewn ffyrdd gwahanol, gan godau byr, mewnblaniadau, teclynnau, fformatau cofnodion, mathau cofnod cyfaddas, opsiynau themâu, meta-flychau, ac elfennau fformatio eraill. Maen nhw’n cynnwys ehangder y swyddogaethau galluoedd WordPress, gydag eglurder profiad cyson y defnyddiwr.

Dychmygwch floc "cyflogai" y byddai cleient y gallu ei lusgo i dudalen Amdanom i arddangos yn awtomatig llun, enw a bio. Bydysawd gyfan o ategion sydd i gyd yn ymestyn WordPress yn yr un ffordd. Dewislenni a gwefannau symlach. Defnyddwyr sy’n gallu deall a defnyddio WordPress yn syth – a 90% o ategion. Bydd hyn yn eich galluogi i gyfansoddi cofnodion hardd fel yr enghraifft hon yn hawdd.

Edrychwch ar y Cwestiynau Cyffredin am atebion i’r cwestiynau mwyaf cyffredin am y prosiect.

Cydweddiad

Mae’r cofnodion yn ôl-gydnaws, a bydd codau byr yn dal i weithio. Rydym yn edrych yn barhaus ar sut y gellir cynnwys metabocsau sydd wedi’u teilwra’n fawr, ac rydym yn edrych ar atebion sy’n amrywio o ategyn i analluogi Gutenberg i ganfod yn awtomatig a ddylid llwytho Gutenberg ai peidio. Er ein bod am sicrhau bod y profiad golygu newydd o ysgrifennu i gyhoeddi yn hawdd ei ddefnyddio, rydym wedi ymrwymo i ddod o hyd i ateb da ar gyfer gwefannau presennol sydd wedi’u teilwra’n arbennig.

Camau Gutenberg

Mae gan Gutenberg dri cham cynllunio. Mae’r cyntaf, sydd wedi’i anelu at gynnwys WordPress 5.0, yn canolbwyntio ar brofiad golygu cofnod a chyflwyno blociau. Mae’r cam cychwynnol hwn yn canolbwyntio ar ddull cynnwys yn gyntaf. Mae’r defnydd o flociau, fel y manylir uchod, yn caniatáu i chi ganolbwyntio ar sut y bydd eich cynnwys yn edrych heb dynnu sylw at opsiynau ffurfweddiad eraill. Bydd hyn yn y pen draw yn helpu pob defnyddiwr i gyflwyno eu cynnwys mewn ffordd sy’n ddifyr, uniongyrchol a gweledol.

Bydd yr elfennau sefydliadol hyn yn paratoi’r ffordd ar gyfer cam dau a thri, a gynlluniwyd ar gyfer y flwyddyn nesaf, i fynd y tu hwnt i’r cofnod i mewn i dempledi tudalen ac yn y pen draw, cyfaddasu gwefannau llawn.

Mae Gutenberg yn newid mawr, a bydd ffyrdd o sicrhau bod y swyddogaeth bresennol (fel codau byr a meta-blychau) yn parhau i weithio wrth ganiatáu i ddatblygwyr yr amser a’r llwybrau i drosglwyddo’n effeithiol. Yn y pen draw, bydd yn agor cyfleoedd newydd ar gyfer datblygwyr ategion a thema i wasanaethu defnyddwyr yn well trwy brofiad mwy deniadol a gweledol sy’n manteisio ar set o offer sy’n cael eu cefnogi an y craidd.

Cyfranwyr

Adeiladwyd Gutenberg gan lawer o gyfranwyr a gwirfoddolwyr. Mae’r rhestr lawn yn CONTRIBUTORS.md .

Cwestiynau Cyffredin

Sut fedra i anfon adborth neu gael help gyda gwall?

Byddem wrth ein bodd yn clywed eich adroddiadau gwallau, awgrymiadau am nodwedd ac unrhyw adborth arall! Dewch draw i dudalen materion GitHub i chwilio am faterion sy’n bodoli eisoes neu agor un newydd. Er y byddwn yn ceisio treialu materion a adroddir yma ar y fforwm ategyn, fe gewch ymateb cyflymach (a lleihau dyblygu ymdrech) trwy gadw popeth yn ganolog yn y storfa GitHub.

Sut fedra i gyfrannu?

Rydym yn galw’r golygydd prosiect hwn "Gutenberg" oherwydd ei fod yn broject mawr. Rydyn ni’n gweithio arno bob dydd yn GitHub, a byddem wrth ein bodd yn cael eich help i’w adeiladu. Mae croeso i chi hefyd roi adborth, yr hawsaf fyddai ymuno â ni yn ein sianel Slack , #core-editor .

Gweler hefyd CONTRIBUTING.md .

Lle ga i ddarllen rhagor am Gutenberg?

Adolygiadau

Exiting but…

I am not code master, it gave many fresh option, but of course there something unpleasant feeling about it.

Waaaa a big no sense

This interface isnt user-friendly. Not hard to understand but completely out of the race versus other solutions.
Nothing works as it should. For a very very basic use, like bbpress, it’s functional. For all the rest ….. useless and a waste of time.

You want to be inspired by something correct? Take Tagdive composer, Elementor and hop, do something usable.

Some examples of irritating bugs
– the live view is wrong
– the content is not aligned as it should during the preview
– missing essential blocks (hero, advanced slider, etc etc)

stop inspiring you from facebook and google tools that are anti-ergonomic.

There are some good things, but mostly I don’t like this editor.

First I would like to say that it was about time for wordpress to have some type of block editor/page builder. I like the blocks and possibilities that we have for text editing.

BUT…

I have issues with adding my custom descriptions in html (text) version of the photos. I get the most stupid warning that the block contains unexpected or invalid content. If I didn’t want that content to be there I wouldn’t put it there.

Also, my posts that are published using Gutenberg editor plug-in don’t show AddThis Share Buttons at all. Why would you block that! I want my social share buttons!!!

I have no idea how to add “nofollow” tag to my links ?!?!?!?!?! There is no option for editing just the link without editing the whole paragraph in html. And even when I do that, it just erases it! rel=”nofollow” is not recognized!!!!
And since it’s not a lot of work, I DON’T WANT TO USE PLUGINS FOR THESE TYPES OF THINGS!!!! I want to be able to edit my text, links and photos in html as I was able with classic editor.

A Page Builder Wannabe

Seems like Gutenberg is a 2nd rate page builder, light years away from WP Bakery, Fusion Builder etc.. Should not be made part of core WP, imho..

Works fine

Good editor, the work is intuitive and goes quickly by the hand…

Competing with Wix… What???

WordPress had FINALLY become a legitimate tool in the industry with a great community of coders and graphic designers helping each other. We just got to a place where we could create beautiful, custom websites for our clients (that didn’t look like ‘wordpress sites’) with all of the great functionality that WP plugins offer… This is a massive setback for serious web developers.

While Gutenberg’s ‘easy block editor’ is not going to magically make people capable of creating beautiful, intuitive websites, I get that it is a great option for people who want SquareSpace simplicity. Why can’t this be an optional plugin? I love the idea of WordPress and BlockPress being two different things – why not?

I have 17 clients on highly customized, complicated WordPress sites. If I didn’t have the ability to disable Gutenberg completely, I would be completely screwed. WordPress, are you listening??

Read all 1,516 reviews

Contributors & Developers

“Gutenberg” is open source software. The following people have contributed to this plugin.

Cyfranwyr

“Gutenberg” has been translated into 41 locales. Thank you to the translators for their contributions.

Translate “Gutenberg” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Cofnod Newid

Latest

  • Allow toggling the core custom fields meta box.
  • Introduce Annotations API across Block and Formatting.
  • Allow using a YouTube URL (or other sources) in the Video block and transparently convert it to Embed.
  • Allow Alt+F10 keyboard shortcut to navigate to block toolbar regardless of the toolbar visibility (isTyping, etc).
  • Return focus to element that opened the post publish panel after it is closed.
  • Avoid unnecessary re-renders when navigating between blocks.
  • Improve interactions around Columns block.
  • Improve keyboard navigation through the Gallery block.
  • Use full parser in do_blocks with nested block support. This switch will allow dynamic blocks which contain nested blocks inside of them and it will pave the way for a filtering API to structurally process blocks.
  • Refactor contextual toolbar to work better with floats.
  • Auto-refresh Popovers position but only refresh if the anchor position changes.
  • Add min-width to audio block.
  • Avoid auto-saving with empty post content.
  • Display correct Taxonomy labels.
  • Fix incorrect import name.
  • Fix styling issue with checkboxes.
  • Add full set of reusable block post type labels (addresses “no blocks found” state).
  • Fix right to left block alignment.
  • Fix “updating failed” notices showing on long-open tabs.
  • Fix default PHP parser to cast inner blocks as arrays.
  • Fix JS/PHP inconsistencies with empty attributes on parsing.
  • Link to the source image in the media block.
  • Fix select all keyboard shortcut for Safari and Firefox.
  • Create multiple blocks when multiple files are drag and dropped.
  • Fixes potential theme syle.css clash.
  • Makes preview button a link (a11y).
  • Stop re-rendering all blocks on arrow navigation.
  • Add constraint tabbing to post publish panel (a11y).
  • Fix image uploading bug (incorrect JSON in apiFetch).
  • Fix taxonomy visibility for contributors.
  • Adds aria labels to images in gallery blocks during editing (a11y).
  • Formatting fix for blockquotes.
  • Hide custom fields when meta box is disabled.
  • Limits blockquote color auto-selection to solid color blocks for readability.
  • Fixes announcement on multi-selection of blocks (a11y).
  • Display upload errors in the image block.
  • Fixes selection of embed type blocks.
  • Fixes JSON attribute parsing.
  • Fixes post publish focus (a11y).
  • Resolve macOS Firefox / Safari sibling inserter behavior.
  • Fix visibility of sibling inserter on tab focus.
  • Fix issue with pasting from Word where an image would be created instead of text.
  • Fix multi-selection for float elements.
  • Fetch all tag terms, not just first 100.
  • Correctly displays media on the right.
  • Only show named image sizes.
  • Improves handling of paste action.
  • Updates displayed permalink after permalink is edited.
  • Adjust font size for contrast warning (a11y).
  • Better handles formatting – nested and Google Docs.
  • Fixes suggestion list scrolling when using keyboard (a11y).
  • Fixes block and menu navigation a11y.
  • Click to close dropdown popover.
  • Fix save lock control.
  • Timezone handling fix.
  • Improve a11y of empty text blocks.
  • Fix states for publish buttons.
  • Fix backspace behavior.
  • Change aria labels for paragraph blocks (a11y).
  • Add support for prepare RichText tree.
  • With this change we force the browser to treat the textarea for the
  • code editor as auto when handling direction for its display to preserve the ability to interact with the block delimiters.
  • Rename parentClientId to rootClientId.
  • Remove deprecated findDOMNode call from Tooltip component.
  • Remove unused ref assignment to RichText.
  • Remove redundant onClickOutside handler from Dropdown.
  • Refactor block state.
  • Remove Cloudflare warning for blocked API calls.
  • Remove _wpGutenbergCodeEditorSettings (dead code).
  • Adds periods to block a11y descriptions.
  • Refactor embed block.
  • Handle metabox warning exceptions.
  • Refactor RichText to update formatting bar on format availability changes.
  • Rename wp-polyfill-ecmascript.
  • Update translator comments for quote and pullquote.
  • Remove findDOMNode useage from NavigableToolbar.
  • Changes handling of dates to properly handling scheduling.
  • Remove findDomNode from withHoverAreas.
  • Fixes missing translator comments.
  • Refactor to import Format API components.
  • Refactor of change detection: initial edits.
  • Adds better translation comments to “resolve” and “resolve block”.
  • Adds option for blocks with child blocks to change selection behavior.
  • Allows blocks to disable being converted to reusable blocks.
  • Improve undo/redo states.
  • Updates parsing to better handle nested content.
  • Remove undefined className argument from save().
  • Use different tooltips for different alignment buttons.
  • Improve performance and handling of autosave.
  • Improve gallery upload for multiple images: load one by one.
  • Adds context variable to RichText component.
  • Avoid calling missing get_current_screen function.
  • Make cssnano remove all style comments.
  • Refactor normalizeBlockType.
  • Shows icon in block toolbar.
  • Makes kitchensink button removable from plugins.
  • Fix popover sizing on screen change (autorefresh)
  • Improvement to Columns block.
  • Update block description for consistency.
  • Refactor block styles registration.
  • Use apostrophe instead of single-quote character in strings.
  • Add transformations between video and media and text block.
  • Version update for NPM packages.
  • Update Lerna to latest version.
  • Validates link format in RichText.
  • Refactor contextual toolbar to work better with floats.
  • Move wp-polyfill-ecmascript override to scripts registration.
  • Improves consistency of parser tests.
  • Remove code coverage.
  • Adds mocking helpers for E2E tests.
  • Runs E2E tests with the user in author role.
  • Adds tests for Format API.
  • Adds E2E test for rapid enter presses.
  • Fix typo in documentation.
  • Fix typos in block API documentation.
  • Improved documentation and examples for withFilters.
  • Fix some broken links in documentation.
  • Fix typo and quote consistency.
  • Remove duplicated word.
  • Adds custom block icon instructions.
  • Update documentation on keyboard shortcuts.
  • Updates isSelectionEnabledDocumentation.
  • Update FontSizePicker component documentation.
  • Export switchToBlockType function.
  • Remove mobile RN test suite (temporary measure).
  • Improve styling of next page block.
  • Removes fixed cover on iOS (unsupported in mobile Safari).
  • Adds support for native media picker.
  • Remove onChange delay.
  • Exposes slot/fill pattern to mobile.
  • Expose @wordpress/editor to mobile.
  • Refreshes native post block merge.
  • Properly handle cancel on the media picker.