7 Comments

  1. T Piwowar

    Does this include persistent notices that appear every time a plug-in’s settings page is viewed that present advertising or appeal for donations, but provide no new information?

    Report

  2. Anh Tran

    I love this requirement. This in the long term will give WordPress users an united experience no matter what theme they are using. That also educate users better and reduce the support effort.

    Report

  3. Caspar Hübinger

    I’ve replied in a note: https://glck.be/10061/

    TL;DR I believe the TRT is trying to solve the problem of a missing API through limitations on an existing one.

    Report

  4. Phil Ingram

    I think it’s in poor taste to force something like this. This doesn’t follow the open and inclusive views of which WP was founded.

    Similar to recent rants about skeleton/starter themes needing to be “full featured” upon activation to be allowed in the repo, defeating the purpose of their existence. Some say this is what Github is for but I say why force one type of user out of the wealth of what the repo provides just because they are not the Theme Team’s preferred type of theme user, all the while these same people are theme authors themselves creating an obvious conflict of competitive interest.

    Who cares, if it’s annoying or not uniform, uninstall the theme if the notice is unwanted, no one is forcing you to use said theme. Otherwise let theme developers provide whatever call-to-action they like upon activation/updates etc. The stifles creativity and there could be a wealth of utility removed by this forceful policy chosen by only only a few. As long as there are no nefarious intentions, leave it be. Does no one research a theme before installing it?

    Report

  5. David McCan

    I think this is a good idea. Standardizing the placement and rules will be a benefit for everyone.

    Report

Comments are closed.

%d bloggers like this: