search

WordPress / wporg-mu-plugins

Development of the Global Header and other mu-plugins used on WordPress.org.
58 stars 28 forks source link

Allow Rosetta users to edit native block menu #51

Open iandunn opened 2 years ago

iandunn commented 2 years ago

49 is adding support for Classic menus on Rosetta sites, to maintain the current functionality. Eventually, though, it'd be better if people could use the new site editor to edit their menus.

We don't want them to override the whole header template, though; they should only be able to edit the "local" items in the menu. https://github.com/WordPress/wporg-news-2021/issues/14 is related

One way to achieve that might be to create a template part for the Rosetta menu items, which is unlocked. The header block could include that, even though the block overall is locked.

Once that's done, we might want to migrate the Classic menus to block menus, and remove all the legacy code.

Otshelnik-Fm commented 2 years ago

Tell me - why was the designer fired? The new menu, the area for translations is terrible.

melchoyce commented 2 years ago

Hey @Otshelnik-Fm, I can understand your frustration, but insulting fellow contributors isn't appropriate or welcome. If you have suggestions for specific improvements to benefit the project, please add them.

Otshelnik-Fm commented 2 years ago

hi @melchoyce. I didn't insult anyone. I see how someone undermines the trust in the resource. And his lack of professionalism. Don't pretend that this is the norm. The suggestion is simple - to discuss and do well right away. And not to roll out a raw something.

iandunn commented 2 years ago

If you're referring to the changes to the content area on translate.w.org, those were unintentional side-effects that I caused, not something any designer intended. They'll be fixed soon.

https://meta.trac.wordpress.org/ticket/6037#comment:5