Гутенберг је више од уређивача. Док је тренутна усредсређеност на уређивачу, пројекат ће утицати на цео доживљај објављивања укључујући прилагођавање (следећи простор усредсређивања).

Сазнајте више о пројекту.

Усредсређеност на уређивање

Уређивач ће направити ново искуство грађења чланака и страна које прави писање богатог садржаја лакшим, и има „блокове“ за прављење лакшим оног што данас могу да буду кратки кôдови, прилагођени HTML или угнежђивања — Matt Mullenweg

Једна ствар која издваја Вордпрес од осталих система је да дозвољава прављење богатих распореда чланака како замислите — али само ако знате HTML и CSS и правите своје сопствене прилагођене теме. Мислећи о уређивачу као алатки која вам дозвољава писање богатих чланака и прављење прелепих распореда, можемо претворити Вордпрес у нешто што корисници воле, супротно од нечега што преузму зато што сви користе.

Гутенберг гледа на уређивач као на нешто више од поља за садржај, преиспитујући распоред који је био умногоме непромењен скоро деценију. Ово нам омогућава холистичко дизајнирање савременог доживљаја уређивања и прављење основе за ствари које долазе.

Ево зашто гледамо на цео екран за уређивање уместо само на поље за садржај:

  1. Блок уједињује више сучеља. Уколико то додамо преко постојећег сучеља, додаће сложеност уместо да је уклони.
  2. Преиспитујући сучеље, можемо осавременити доживљај писања, уређивања и објављивања, имајући у виду корисност и једноставност, која доноси корист и новим и неформалним корисницима.
  3. Када једно сучење блока преузме главну сцену, показује јасну путању напред за градитеље да праве премијум блокове, супериорне у односу и на кратке кôдове и виџете.
  4. Узимамо у обзир да цело сучење поставља основу за следеће фокус, прилагођавање целог веб места.
  5. Гледање на пун екран уређивача такође нам даје прилику да драматично осавременимо основу и направимо кораке напред према флуиднијом и будућности коју покреће Јаваскрипт који потпуно користи Вордпресом REST API.


Blocks are the unifying evolution of what is now covered, in different ways, by shortcodes, embeds, widgets, post formats, custom post types, theme options, meta-boxes, and other formatting elements. They embrace the breadth of functionality WordPress is capable of, with the clarity of a consistent user experience.

Imagine a custom “employee” block that a client can drag to an About page to automatically display a picture, name, and bio. A whole universe of plugins that all extend WordPress in the same way. Simplified menus and widgets. Users who can instantly understand and use WordPress — and 90% of plugins. This will allow you to easily compose beautiful posts like this example.

Погледајте ЧПП за одговоре на најчешћа питања о пројекту.


Posts are backwards compatible, and shortcodes will still work. We are continuously exploring how highly-tailored metaboxes can be accommodated, and are looking at solutions ranging from a plugin to disable Gutenberg to automatically detecting whether to load Gutenberg or not. While we want to make sure the new editing experience from writing to publishing is user-friendly, we’re committed to finding a good solution for highly-tailored existing sites.

Фазе Гутенберга

Gutenberg has three planned stages. The first, aimed for inclusion in WordPress 5.0, focuses on the post editing experience and the implementation of blocks. This initial phase focuses on a content-first approach. The use of blocks, as detailed above, allows you to focus on how your content will look without the distraction of other configuration options. This ultimately will help all users present their content in a way that is engaging, direct, and visual.

These foundational elements will pave the way for stages two and three, planned for the next year, to go beyond the post into page templates and ultimately, full site customization.

Gutenberg is a big change, and there will be ways to ensure that existing functionality (like shortcodes and meta-boxes) continue to work while allowing developers the time and paths to transition effectively. Ultimately, it will open new opportunities for plugin and theme developers to better serve users through a more engaging and visual experience that takes advantage of a toolset supported by core.


Гутенберг је направљен од стране многих сарадника и добровољаца. Молимо вас да погледате цео списак у CONTRIBUTORS.md.


How can I send feedback or get help with a bug?

We’d love to hear your bug reports, feature suggestions and any other feedback! Please head over to the GitHub issues page to search for existing issues or open a new one. While we’ll try to triage issues reported here on the plugin forum, you’ll get a faster response (and reduce duplication of effort) by keeping everything centralized in the GitHub repository.

Како могу да допринесем?

We’re calling this editor project „Gutenberg“ because it’s a big undertaking. We are working on it every day in GitHub, and we’d love your help building it.You’re also welcome to give feedback, the easiest is to join us in our Slack channel, #core-editor.

Такође погледајте CONTRIBUTING.md.

Где могу да прочитам више о Гутенбергу?


Complete breach of privacy

As soon as I installed Gutenberg, it posted an advertisement article on my website an sent advertising emails to all my subscribers using me as the authors for the article and the emails. I don’t remember Gutenberg asking permission to do that, that’s something I would’ve remembered. No plugin ever should use your website and your subscribers to advertise themselves, and on top of that write a signature as if you’re the one who sent those emails and wrote that article.

What A Wasted Opportunity

As a preface: I make well into six-figures a year building advanced WordPress websites for high end clients. I’ve done this for eight years now. My business is known in my city as being the top WordPress expert.

That said, Gutenberg feels counterintuitive. We solely use page builders on client sites now, like Elementor, so when I heard about Gutenberg, I was really excited to see a native page builder come into play. Then I tried it. Divi and Visual Composer, both the bane of my existence, feel more intuitive, and they’re both literal nightmares to work with.

Gutenberg seems to be suffering from one major issue: it doesn’t know what it wants to be. Is it a page builder? Is it an editor? How in the world can you build a page builder without a functional grid system? Why is it compulsory? Why is it replacing metaboxes, such a core feature of WP?

It seems too much time has went into this for it to be abandoned. Apparently the WordPress team will not listen to the vast cries from its core base. I hope the best for the project, but if it interferes with my business, I’ll be the first railing against it. This could have been done way better and the implementation of Gutenberg at the core of WP is a huge mistake — perhaps one of the biggest I’ve seen in software dev.

Awful editor

I get what the wordpress team was trying to achieve with the new Gutenberg editor, and I suppose it probably works great for people who want create media heavy posts with unusual layouts. But the editor has turned into a „What you see is what you *might* get“.

Just writing some text in a nice layout with and image or code block here and there is tedious and far more trouble to get done with the new Gutenberg editor.

No thank you. If this ever becomes mandatory, I’ll happily migrate 10+ years of posts and comments to something that isn’t wordpress.

Too many blocks: slows us down

My biggest gripe is that it will slow us writers down.

It’s too many blocks.
In my opinion it’s better if the main text blocks do replicate every time you press enter.
That’s distracting and unwieldy when you write long, authoritative posts.

I hope it’s a teething problem because otherwise I see great potential.

Please also allow us to use blocks that run all along the page horizontally, so we can create nice colored strips for good landing pages for products (so far the background color is almost useless otherwise).

Not suited for professionals

I find Gutenberg to be ill suited for professional use.
it might be nice for people who are complete strangers to HTML\CSS, but to professional that are used to edit the code themselves, this editor is very frustrating.

It feels like a dumbed down version aimed at bloggers without any technical skills.

I can’t work with it, I’m going to be sticking with the Classic editor.

And what’s with the 610px width? is that a joke?

Види сва 1.572 прегледа

Сарадници и градитељи

„Гутенберг“ је софтвер отвореног кода. Следећи људи су допринели овом додатку.


„Гутенберг“ је преведен на 42 језика. Хвала преводиоцима за њихове доприносе.

Преведите „Гутенберг“ на свој језик.

Заинтересовани сте за градњу?

Прегледајте код, проверите SVN складиште или се пријавите на белешку градње преко RSS-а.

Белешка о изменама


  • Raw Handling: fix consecutive lists with one item
  • Avoid showing draft revert message on autosaves
  • Honor the Disable Visual Editor setting in the Gutenberg editor page
  • Docs: Fix dead links in CONTRIBUTING.md
  • Fix undefined index warnings in Latest Comments & Latest Posts
  • Add react-native module property to html-entities package.json
  • RichText: List: Sync DOM after editor command
  • Fix RichText infinte rerendering
  • Fix keycodes package missing i18n dependencies