WordPress has some objectives, a rationale and a philosophy of use that is what has contributed to the fact that today he is the king of CMS and that it remains so for many years, if you keep the principles of its philosophy, this …
Out of the box
A great software should work with little configuration and adjustments . WordPress is designed to be up and running in full in no more than five minutes. You should not have to fight to use the standard WordPress functionality.
We work hard to ensure that each release maintains this philosophy. We ask for the minimum possible technical details during the installation process and we offer full explanations of everything we ask for.
Designed for most
Many WordPress end users are not technically prepared. They do not know what AJAX is, nor do they care what version of PHP they are using. The average WordPress user simply wants to be able to write without problems or interruptions. These are the users for whom we design the software since in the end they are the ones who will spend the most time using it for what it was created.
Decisions, not options
When we make decisions, the users are the that we have in mind first A good example of this consideration are the software options. Every time you give an option to a user you are asking him to make a decision. When a user does not care or does not understand the option this leads to frustration. As developers, we sometimes feel that offering options for everything is a good thing, because you never have too many things to choose, right? In the end, these options end up being technical decisions, choices in which the average user has no interest whatsoever. It is our obligation, as developers, to make intelligent design decisions and avoid putting the weight of technical decisions on the end user.
Clean, light and average
The WordPress core will always offer a solid range of basic features. It is designed to be light and fast, and it will always be like this. We constantly ask " when feature X " or " will be mounted why is not plugin X integrated into the kernel ". The golden rule is that the core must offer features that 80% or more of the end users will truly appreciate and use. If the next version of WordPress comes with a feature that most users want to disable immediately, or they think they will never use it, then we will remove it. If we stay at the beginning of 80% this should never happen.
We are able to do this since we have a very capable plugins and themes system, and a fantastic community of developers. Different people have different needs, and having a huge number of quality WordPress plugins and themes allows users to customize the facilities to their liking. This should allow all users to find the remaining 20% and make WordPress features that everyone appreciates and uses.
The struggle for simplicity
We never have enough simplicity. We want to make WordPress easier to use in each version. We have a good track record in this regard, and if you do not believe us then check out some of the older versions of WordPress!
In the latest versions we have taken big steps to improve the ease of use and make things better. really easier to understand. A great example of this is the kernel software updates. Upgrading used to be a painful manual task, too compiled for most users. We decided to focus on this and simplify it until we get it in a single click. Now anyone who has a WordPress installation can do one-click updates, both with the WordPress kernel and with the plugins and themes.
We love challenging ourselves and simplifying tasks to get positive results for the overall user experience. with WordPress. Each version of WordPress should be easier and more pleasant to use than the previous one.
Deadlines are not arbitrary
Deadlines are not arbitrary, they are a promise we make to ourselves and our users to help us to control the infinite possibilities of everything that could be part of each version. We aspire to launch three major versions a year because based on successes and mistakes we have discovered that it is a good balance between offering cool things in each version and not ending up doing so much that we break more than we add.
Meet deadlines almost It always forces you to remove something from each version. And this is not a bad thing, it is what it should be.
The routine of delaying a version to get " that feature most " is, literally, a warren. We did it for a year, and it was not pleasant for anyone.
The more frequent and regular the versions the less important it is for each specific characteristic to be in that version. If it is not available for this version it will be in a few months, in the following one. When the versions are unpredictable, or lengthen or shorten, there is more pressure to try to put in them more than one thing because it will spend a lot of time until the next. The delay begets delay.
The loquacious minority
There is a good rule of thumb in Internet culture called the 1% rule. It states that " the number of people creating content on the Internet represents approximately 1% (or less) of the people who see that content ."
So, although we consider it really important to listen and respond to all those who post comments and express their opinions in forums, they only represent a fraction of our end users. When we make decisions about how to move forward with future versions of WordPress we try to involve more of those users who are not so talkative in the network. We do it by meeting and talking with WordCamps users all over the world, this gives us a better balance and understanding, and in the end it allows us to make better decisions so that everything goes forward.
Our bill of rights
WordPress is under the General Public License (GPL v2 or later), which offers four fundamental freedoms, considered as the WordPress "declaration of rights":
- The freedom to execute the program, for any purpose.
- Freedom to study how the program works, and change it to make it do what you want.
- The freedom to redistribute it.
- The freedom to distribute copies of your modified versions to others.
Part of these requirements of the The license includes also collecting in the GPL license the derivative works or elements that link to WordPress core functions (such as themes, plugins, etc.), transmitting in this way the I also think that there are people who will try to bypass these ideals and restrict freedom to their users, trying to find loopholes or any way to circumvent the intention of the WordPress license, which is to ensure freedom of use. We believe that the community as a whole will reward those who focus on supporting the freedoms of this license rather than those who try to prevent them.
Responsible use of WordPress community resources should therefore be subject to best use possible, emphasizing high-quality collaborations that encompass the freedoms offered by the GPL.