├── EN └── WHY.md ├── LICENSE └── README.md /EN/WHY.md: -------------------------------------------------------------------------------- 1 | # WordPress is a universally trusted platform 2 | 3 | Currently, WordPress powers about 24% of the *World Wide Web* sites (2015, [W3Techs.com](http://w3techs.com/technologies/details/cm-wordpress/all/all)). 4 | 5 | ## WordPress is trusted by many big brands 6 | * [Time.com](https://wordpress.org/showcase/time-com/) 7 | * [New York Times](https://wordpress.org/showcase/ny-times-blogs/) 8 | * [Microsoft](https://wordpress.org/showcase/microsoft-news-center/) 9 | * [Sony Music](https://wordpress.org/showcase/sony-music/) 10 | * [eBay](https://wordpress.org/showcase/ebay-ink/) 11 | * [Toyota](https://wordpress.org/showcase/toyota-motors-brasil/) 12 | * [Sweden](https://wordpress.org/showcase/swedens-official-site/) 13 | * [Other Fortune 500 websites](https://wordpress.org/showcase/tag/fortune-500/) 14 | 15 | 16 | # WordPress is easy to maintain 17 | There are many good WordPress developers, and the standards are well documented. 10 years from now it will not be a problem to implement a new feature on your website. 18 | Currently, there are 37,372 free plugins and on on of the theme marketplaces (themeforest.com) there are 5323 themes available. 19 | If a need arises to add a functionality 20 | 21 | ## Everything is possible 22 | Extensibility is at the core of WordPress. 23 | Most certainly, it is possible to accomodate your business needs, or any other website structure imaginable. 24 | 25 | Everything possible in any other CMS can be also implemented in WordPress, but much easier. 26 | 27 | # Building on top of WordPress is cheaper and faster 28 | 29 | We like to focus on making your website stand out. Implementing base requirements will just take time and budget. WordPress provides extremely well-tested and robust foundation for your new spectacular website. 30 | 31 | # WordPress is very well documented 32 | [Codex.wordpress.com](http://codex.wordpress.com) provides an extensive documentation of every feature of WordPress. Additionally, [WordPress.tv](http://wordpress.tv/) provides video tutorials. 33 | 34 | # WordPress is tested and secure 35 | Bilions of people visit website built with WordPress. This kind of live test coverage is not easy to replicate. 36 | More than 2000 people (TODO: reference needed) contributed to WordPress uncovering vulnerabilities and fixing bugs making it the most reviewed CMS in the world. 37 | 38 | # WordPress is fixed really fast 39 | Whenever a vulnerability or a bug is uncovered in WordPress, the community or Automattic (the company overseeing WordPress development) fixes it really fast (TODO: stats needed) and pushes an automatic update. Additional personnel is not needed, even years after website development. 40 | 41 | Contrary, custom solutions lack 10 years of live tests on bilions of users. Even if vulnerability or a bug is identified, the solution has to be implemented. 42 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2015 Artur Piszek 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | 23 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Why-WordPress 2 | Arguments for convincing a prospective client that he/she should choose WordPress. 3 | 4 | Updated with **Matt Mullenweg`s** answer from WordCamp Europe 2015 5 | 6 | **TLDR:** [WHY?](./EN/WHY.md) 7 | 8 | # Why 9 | Have you ever had to create a presentation, document or a development plan in which you had to convince your (prospective) client to go with WordPress instead of Sharepoint / or (god forbid) `custom CMS built from scratch` ? 10 | 11 | I had to, **many** times. 12 | 13 | **We all** know WordPress is awesome. But the client doesen't know that. All he heard were security concerns, that `Ghost` will kill WordPress, and so on. 14 | 15 | I know, WordPress.org has a showcase site, where you can see all the beautifull website built with it, but the format is hard to include in presentations and documents. 16 | 17 | # What is this? 18 | This is a collection of arguments, presentations and documents to include into your own portfolio / development plan. 19 | 20 | # Gimme! 21 | 22 | [I started with basic arguments in English language.](./EN/WHY.md) 23 | 24 | # Please Contribute! 25 | This is a work in progress started a day before `Wordcamp Europe`. I hope this helps :). 26 | 27 | I think it would be best to stick with Markdown format, but everything goes :) 28 | Please, fork this repo and write! 29 | 30 | ### TODO 31 | * More slide bullet points 32 | * More convincing argumentation 33 | * Other languages 34 | --------------------------------------------------------------------------------