|
|
| Line 1: |
Line 1: |
| {{Community_Page}}
| |
| {{CMS_Infobox | | {{CMS_Infobox |
| | name = WordPress | | | name = WordPress |
| | status = Community | | | developer = WordPress Foundation / Automattic |
| | type = Blog / CMS | | | type = Blogging CMS / Website Builder |
| | license = GPL v2 | | | license = GNU General Public License v2 |
| | language = PHP | | | language = PHP |
| | database = MySQL / MariaDB | | | released = 2003-05-27 |
| | latest_ver = 6.6 | | | latest_version = 6.5.x |
| | release_date = May 27, 2003
| | | website = https://wordpress.org |
| | website = https://wordpress.org | | | github = https://github.com/WordPress/WordPress |
| | github = https://github.com/WordPress/WordPress | | | stars = 19,000+ |
| | demo = https://wordpress.com | |
| }} | | }} |
| | |
| | '''WordPress''' is a free and open-source content management system written in [[PHP]] and paired with a database. As of 2024, WordPress powers over '''43%''' of all websites on the internet. |
|
| |
|
| == Overview == | | == Overview == |
| '''WordPress''' is a free and open-source [[Category:PHP_CMS|content management system]] written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system, referred to within WordPress as "Themes". Originally created as a blogging system in 2003, WordPress has evolved to support other types of web content, including traditional mailing lists and forums, media galleries, membership sites, learning management systems (LMS), and online stores via extensions such as [[WooCommerce]]. | | WordPress was originally created by '''Matt Mullenweg''' and '''Mike Little''' as a fork of b2/cafelog in 2003. What began as a simple blogging platform has evolved into a full-featured website builder. |
| | | The WordPress ecosystem is defined by its massive library of over '''59,000 free plugins''' in the official repository and more than '''10,000 free themes'''. |
| As of 2024, WordPress powers over 43% of the top 10 million websites on the internet and commands a market share of more than 62% among websites built with a identifiable content management system. Its immense popularity is driven by its ease of use, extensive plugin ecosystem, strong community support, and open-source licensing model. WordPress is released under the GNU General Public License version 2 (or later).
| |
| | |
| The platform is developed and maintained by a global community of open-source contributors, coordinated through [[WordPress.org]], while commercial services, trademark management, and hosted instances are managed by [[Automattic]] and the WordPress Foundation. | |
| | |
| == History ==
| |
| WordPress was born in May 2003 as a fork of '''b2/cafelog''', a blogging platform developed by Michel Valdrighi. When Valdrighi discontinued development on b2/cafelog, Matt Mullenweg and Mike Little decided to build a new platform on top of the original b2 codebase.
| |
| | |
| * '''2003 (Version 0.70)''': Released on May 27, 2003, featuring an updated interface, simplified installation process, and XHTML-compliant template output.
| |
| * '''2004 (Version 1.2 "Mingus")''': Introduced the Plugin Architecture, enabling third-party developers to extend core functionality without modifying source files.
| |
| * '''2005 (Version 1.5 "Strayhorn")''': Introduced the Theme System and Template Hierarchy, establishing a clear separation between design presentation and content structure.
| |
| * '''2007 (Version 2.1 – 2.3)''': Redesigned admin interface, introduced taxonomy tags, auto-save capabilities, and spell checking.
| |
| * '''2010 (Version 3.0 "Thelonious")''': Merged WordPress MU (Multisite) into the core release, introduced Custom Post Types, custom taxonomies, and custom menu management.
| |
| * '''2015 (Version 4.4 "Clifford")''': Added the initial infrastructure for the native WordPress REST API into core.
| |
| * '''2018 (Version 5.0 "Bebo")''': Major milestone introducing the Gutenberg Block Editor, replacing the classic WYSIWYG editor (TinyMCE) with a modern component-based editor built on React.
| |
| * '''2022 (Version 5.9 & 6.0)''': Introduced Full Site Editing (FSE), block-based themes, global typography styles, and the `theme.json` configuration standard.
| |
| * '''2024 (Version 6.5 & 6.6)''': Released enhanced features including the Font Library, pattern overrides, block bindings API, and improved performance metrics.
| |
|
| |
|
| == Key Features == | | == Key Features == |
| * '''Gutenberg Block Editor''': Modular editor treating every paragraph, heading, image, or widget as an independent block, allowing rich visual layouts without code. | | * '''Block Editor (Gutenberg)''' — Modern drag-and-drop page builder |
| * '''Theme & Template System''': Comprehensive design customization supporting traditional PHP template hierarchies as well as modern FSE block templates.
| | * '''Theme System''' — Thousands of themes for complete visual customization |
| * '''Plugin Ecosystem''': Extensible architecture supported by over 60,000 free plugins hosted on the official WordPress directory.
| | * '''Plugin Architecture''' — Extendable via 59,000+ plugins |
| * '''REST API Integration''': Built-in JSON REST API allowing WordPress to operate as a headless CMS or power external mobile apps and front-end frameworks like React or Next.js.
| | * '''WooCommerce Integration''' — Transform any WordPress site into a full eCommerce store |
| * '''Multisite Network''': Built-in feature enabling site administrators to create and manage multiple virtual websites from a single WordPress installation and database.
| | * '''REST API''' — Full JSON REST API for headless/decoupled architectures |
| * '''User Roles & Permissions''': Granular access control system supporting default roles (Administrator, Editor, Author, Contributor, Subscriber) and custom role permissions.
| |
| * '''Media Management''': Integrated media library with drag-and-drop uploads, image editing, automatic generation of responsive image sizes (`srcset`), and WebP format support.
| |
| * '''Custom Post Types & Taxonomies''': Capability to create structured data models beyond standard Posts and Pages, such as Products, Portfolios, or Events. | |
| | |
| == Architecture ==
| |
| WordPress relies on a classic model-view-controller-like pattern built with PHP and backed by a relational database management system (RDBMS) such as MySQL or MariaDB.
| |
| | |
| === File & Directory Structure ===
| |
| A typical WordPress installation is structured into several primary core directories:
| |
| * <code>wp-config.php</code>: Core configuration file containing database credentials, table prefixes, security salts, and constant definitions.
| |
| * <code>wp-content/</code>: Directory storing user modifications, including:
| |
| ** <code>wp-content/themes/</code>: Installed theme templates and styling assets.
| |
| ** <code>wp-content/plugins/</code>: Installed third-party plugin extensions.
| |
| ** <code>wp-content/uploads/</code>: Media assets uploaded via the WordPress admin dashboard.
| |
| ** <code>wp-content/mu-plugins/</code>: Must-Use plugins executed automatically before standard plugins.
| |
| * <code>wp-includes/</code>: Core library classes, helper functions, and database abstraction layers.
| |
| * <code>wp-admin/</code>: Administration backend controllers, dashboard interfaces, and management scripts.
| |
| | |
| === Hooks System: Actions and Filters ===
| |
| Extensibility in WordPress is powered by an event-driven event hook architecture consisting of **Actions** and **Filters**:
| |
| * '''Actions (<code>add_action</code>)''': Code hooks invoked at specific execution events (e.g., <code>init</code>, <code>wp_enqueue_scripts</code>, <code>save_post</code>). Actions perform execution routines without altering return values directly.
| |
| * '''Filters (<code>add_filter</code>)''': Code hooks designed to intercept, modify, and return data before it is saved to the database or output to the browser (e.g., <code>the_content</code>, <code>wp_title</code>).
| |
| | |
| === Template Hierarchy ===
| |
| When a user requests a URL, WordPress queries the database and evaluates the request using a fallback mechanism known as the **Template Hierarchy**. For example, when rendering a single blog post, WordPress searches for:
| |
| # <code>single-{post-type}-{slug}.php</code>
| |
| # <code>single-{post-type}.php</code>
| |
| # <code>single.php</code>
| |
| # <code>singular.php</code>
| |
| # <code>index.php</code>
| |
| | |
| == Themes ==
| |
| Themes define the visual appearance, presentation logic, and user layout of a WordPress site.
| |
| | |
| === Classic Themes vs. Block Themes ===
| |
| * '''Classic Themes''': Built using PHP files (such as <code>header.php</code>, <code>footer.php</code>, <code>single.php</code>) combined with CSS and JavaScript. Classic themes rely on WordPress template tags and functions inside <code>functions.php</code> to render content. | |
| * '''Block Themes''': Introduced alongside Full Site Editing (FSE). Block themes use HTML templates containing block markup (e.g., <code>templates/index.html</code>) located inside the theme directory, allowing non-developers to edit all areas of a site within the admin block editor.
| |
| | |
| === Full Site Editing (FSE) & theme.json ===
| |
| Full Site Editing allows users to edit headers, footers, sidebars, and global templates directly through the WordPress admin interface. Block themes utilize a centralized configuration file named <code>theme.json</code>, which defines:
| |
| * Global color palettes and gradient presets.
| |
| * Typography scales, custom font families, and line heights.
| |
| * Content and wide layout container dimensions.
| |
| * Default block settings and custom CSS properties.
| |
| | |
| == Plugins ==
| |
| Plugins are self-contained PHP scripts that hook into WordPress core execution to add features, integrations, or security capabilities. The official WordPress.org Plugin Directory hosts over 60,000 free open-source plugins.
| |
| | |
| === Notable Plugins ===
| |
| * '''[[WooCommerce]]''': The leading e-commerce framework for WordPress, enabling product catalog management, payment gateway integration, and shipping management. | |
| * '''Yoast SEO / Rank Math''': Complete search engine optimization suites offering meta tags management, XML sitemaps, schema structured data, and content analysis.
| |
| * '''Elementor / Divi''': Visual drag-and-drop site builders providing real-time design customizers outside the core block editor.
| |
| * '''Contact Form 7 / WPForms''': User-friendly form generators handling user submissions, notifications, and anti-spam integrations. | |
| * '''WP Rocket / W3 Total Cache''': Performance optimization plugins delivering page caching, browser caching, CDN integration, and asset minification.
| |
| | |
| == WooCommerce ==
| |
| '''WooCommerce''' is an open-source e-commerce plugin designed specifically for WordPress. Developed originally by WooThemes and acquired by Automattic in 2015, WooCommerce powers over 30% of all online stores globally.
| |
| | |
| It turns a standard WordPress installation into a full-featured online store with capabilities including:
| |
| * Management of physical, digital, and variable products.
| |
| * Built-in shipping calculators and tax rate rules.
| |
| * Native integration with major payment processors like Stripe, PayPal, and Square.
| |
| * Extensibility via thousands of dedicated WooCommerce extension plugins.
| |
|
| |
|
| == REST API == | | == Installation == |
| Integrated into core in version 4.7, the '''WordPress REST API''' provides HTTP REST endpoints allowing developers to interact with a WordPress site remotely using JSON objects.
| | === Requirements === |
| | * PHP 7.4 or higher |
| | * Database server |
| | * Web Server (Apache or Nginx) |
|
| |
|
| Endpoints follow the standard URI structure `/wp-json/wp/v2/` for resources such as posts, pages, media, users, and custom post types.
| | === Quick Start === |
| | 1. Download the latest version from WordPress.org. |
| | 2. Upload the files to your web server. |
| | 3. Create a database for WordPress to use. |
| | 4. Visit your domain in a browser to complete the 5-minute setup wizard. |
|
| |
|
| === Headless WordPress === | | == API Reference == |
| Using WordPress in a **headless** configuration decouples the back-end content management system from the front-end rendering layer. In a headless setup:
| | WordPress ships with a full '''REST API''' available at the `/wp-json/wp/v2/` endpoint. You can retrieve posts, pages, and custom post types using standard HTTP requests. |
| * WordPress serves solely as a content database and administration interface.
| |
| * Front-end single-page applications or static sites are built using modern frameworks like React, Next.js, Vue, or Nuxt, fetching content dynamically via the REST API or GraphQL (via WPGraphQL).
| |
|
| |
|
| == Hosting == | | == Pricing == |
| WordPress can be deployed in two primary environments: | | WordPress itself is '''completely free and open source'''. Costs are associated with hosting, domain registration, and optional premium themes or plugins. |
|
| |
|
| === WordPress.com vs. WordPress.org === | | == Pros & Cons == |
| * '''WordPress.org''' (Self-Hosted): Free, open-source software downloaded from WordPress.org. Webmasters install it on their own web hosting server, providing complete control over code, plugins, database, and themes.
| | {| class="wikitable" |
| * '''WordPress.com''' (Hosted SaaS): A commercial hosted platform run by Automattic. It offers free and paid subscription plans with automated updates, maintenance, and hosting managed out of the box, with varying restrictions based on the plan tier.
| | ! ✅ Pros !! ❌ Cons |
| | |
| === Server Requirements & Recommended Hosting ===
| |
| To run WordPress effectively, servers should meet the following minimum recommendations:
| |
| * '''PHP''': Version 7.4 or higher (PHP 8.2+ recommended).
| |
| * '''Database''': MySQL version 5.7+ or MariaDB version 10.4+.
| |
| * '''Web Server''': Nginx or Apache HTTP Server with `mod_rewrite` enabled.
| |
| * '''Protocol''': HTTPS (SSL/TLS certificate) support.
| |
| | |
| Popular host types include shared hosting, Virtual Private Servers (VPS), containerized cloud instances, and specialized Managed WordPress Hosting platforms (such as WP Engine, Kinsta, Pressable, and Cloudways).
| |
| | |
| == Security ==
| |
| Due to its dominant market share, WordPress is a frequent target for cyber attacks. While WordPress core is continuously audited by a dedicated security team, vulnerabilities most frequently arise from outdated plugins, poorly coded third-party themes, or misconfigured server environments.
| |
| | |
| === Common Attack Vectors ===
| |
| * '''Cross-Site Scripting (XSS)''': Injection of malicious scripts through un-sanitized user inputs.
| |
| * '''SQL Injection (SQLi)''': Executing unauthorized SQL commands through un-escaped database queries.
| |
| * '''Brute-Force Attacks''': Automated login attempts targeted at `wp-login.php` or `xmlrpc.php`.
| |
| * '''Cross-Site Request Forgery (CSRF)''': Exploiting user authentication sessions to perform unintended admin actions.
| |
| | |
| === Security Best Practices ===
| |
| * Maintaining prompt updates for WordPress core, themes, and plugins.
| |
| * Enforcing strong password policies and multi-factor authentication (2FA).
| |
| * Disabling file editing in the admin panel using `define('DISALLOW_FILE_EDIT', true);`.
| |
| * Using Web Application Firewalls (WAF) and security plugins like Wordfence or Sucuri.
| |
| * Implementing proper file permissions (typically `755` for directories and `644` for files).
| |
| | |
| == Comparison ==
| |
| The following table highlights key differences between WordPress and other popular open-source content management systems:
| |
| | |
| {| class="wikitable sortable" style="width:100%;" | |
| ! CMS Platform !! Primary Focus !! Technical Complexity !! Extensibility !! Global Market Share !! Core Language | |
| |-
| |
| | '''[[WordPress]]''' || General CMS & Blogging || Low to Medium || High (60,000+ plugins) || ~62% CMS market share || PHP
| |
| |- | | |- |
| | '''[[Drupal]]''' || Enterprise & Complex Portals || High || High (Modules ecosystem) || ~2% CMS market share || PHP | | | Largest ecosystem (59,000+ plugins) || Plugin conflicts are common |
| |- | | |- |
| | '''[[Joomla]]''' || Structured Portals & Communities || Medium to High || Medium (Components/Modules) || ~2.5% CMS market share || PHP | | | Beginner-friendly admin interface || Performance requires optimization |
| |- | | |- |
| | '''[[Ghost]]''' || Modern Publishing & Newsletters || Low || Medium (Integrations/Webhooks) || <1% CMS market share || Node.js / JavaScript | | | Free and open source || Security vulnerabilities via outdated plugins |
| |} | | |} |
|
| |
| == Community ==
| |
| The WordPress project is supported by a large global community of developers, designers, writers, and users:
| |
|
| |
| * '''[[WordPress.org]]''': The official central hub for downloading core software, themes, and plugins, as well as accessing developer documentation and community support forums.
| |
| * '''WordCamp''': Locally organized, informal conferences organized by volunteers to discuss WordPress development, business, design, and content strategies worldwide.
| |
| * '''Make WordPress''': Global contribution teams focusing on various pillars of the platform, including Core development, Design, Documentation, Accessibility, Polyglots (localization), and Security.
| |
|
| |
|
| == External Links == | | == External Links == |
| * [https://wordpress.org Official Website] | | * [https://wordpress.org Official Website] |
| * [https://wordpress.org/plugins/ Plugin Directory]
| | * [https://developer.wordpress.org Developer Documentation] |
| * [https://wordpress.org/themes/ Theme Directory]
| |
| * [https://developer.wordpress.org/ Developer Documentation] | |
| * [https://github.com/WordPress/WordPress GitHub Repository]
| |
|
| |
|
| [[Category:CMS_Platforms]] | | [[Category:CMS_Platforms]] |
| [[Category:Blogging_CMS]] | | [[Category:Blogging_CMS]] |
| [[Category:Open_Source_CMS]] | | [[Category:Open_Source_CMS]] |
| [[Category:PHP_CMS]]
| |
