Revision 1

WordPress

@namkyu · Sep 3, 2026, 8:45 AM

Added WordPress.org vs WordPress.com, setup, practical workflows, plugins, business uses, maintenance, APIs, and alternatives.
+17,1090

WordPress is an open-source content management system used to build websites, blogs, online stores, membership sites, directories, publications, and other web-based businesses.

The WordPress software itself is free, but a self-hosted WordPress website normally requires separate hosting and a domain. Its main advantage is flexibility: themes and plugins can turn the same core system into anything from a simple blog to an e-commerce store or custom web application.

Item

Details

Main use

Building and managing websites

Best for

Blogs, business websites, content sites, ecommerce, and custom websites

Core software

Free and open source

License

GPLv2 or later

Hosting

Required separately for self-hosted WordPress

Domain

Required separately for a custom site

Website share

More than 43% of the web according to WordPress.org

Free plugins

71,000+ in the official directory

Themes

Thousands of free and commercial options

Ecommerce

Available through plugins such as WooCommerce

API

Built-in REST API

Coding required

No for basic sites; useful for advanced customization

The WordPress software available from WordPress.org is free.

There is no WordPress.org subscription fee or per-transaction platform fee for using the core software commercially.

A realistic self-hosted WordPress site can still involve costs for:

  • Domain registration

  • Web hosting

  • Premium themes

  • Premium plugins

  • Backups

  • Email services

  • Development

  • Maintenance

The practical cost depends more on the website's hosting and plugin stack than on WordPress itself.

These are related but different services.

WordPress.org provides the open-source WordPress software that can be installed on your own hosting.

WordPress.com is a hosted service with its own free and paid plans.

A typical self-hosted setup is:

Domain → Hosting → Install WordPress → Choose theme → Add plugins → Publish site

A WordPress.com setup is:

Create WordPress.com account → Choose hosted plan → Build site

For businesses that want maximum control over hosting, plugins, data, and customization, self-hosted WordPress is usually the more relevant version.

WordPress provides the underlying system for managing:

  • Pages

  • Posts

  • Images and media

  • Users

  • Categories

  • Tags

  • Navigation

  • Themes

  • Plugins

A normal content workflow looks like:

Create article → Add images → Choose categories → Publish → Search engines crawl page → Update article later

Plugins can extend this into more specialized workflows.

For example:

WordPress → WooCommerce → Products → Checkout → Orders

or:

WordPress → Membership plugin → Paid member → Restricted content

or:

WordPress → Form plugin → Lead submission → CRM

This extensibility is one of the main reasons WordPress can support many different business models.

Choose a domain that the business controls independently.

Keeping the domain separate from the website software makes it easier to change hosting providers later.

A host needs to provide a server environment capable of running WordPress.

WordPress currently recommends:

  • PHP 8.3 or greater

  • MariaDB 10.11 or greater, or MySQL 8.0 or greater

  • HTTPS support

Apache or Nginx is recommended, although WordPress can run on other compatible web servers.

For a beginner, managed WordPress hosting can reduce setup and maintenance work.

Many hosting providers provide one-click installation.

After installation, the main administrative interface is commonly accessed through:

yourdomain.com/wp-admin/

From there, the site owner manages content, plugins, themes, users, and settings.

A theme controls the site's presentation.

It can determine:

  • Typography

  • Colors

  • Header

  • Footer

  • Page layouts

  • Blog layouts

  • Responsive behavior

Start with a lightweight theme that already supports the required layout.

Do not choose a theme simply because its demo contains many visual effects.

Plugins extend WordPress functionality.

Examples include:

  • SEO

  • Forms

  • Ecommerce

  • Security

  • Caching

  • Backups

  • Memberships

  • Analytics

Install plugins because the site needs a specific capability, not because a plugin appears useful.

A business website commonly begins with pages such as:

  • Home

  • About

  • Services or Products

  • Contact

  • Privacy Policy

Content-driven websites can then add articles through WordPress Posts.

WordPress separates more permanent content from chronological content.

Pages are typically used for:

  • About

  • Services

  • Contact

  • Landing pages

Posts are normally used for:

  • Articles

  • News

  • Tutorials

  • Blog content

For a Blogging business, Posts usually make up most of the content library.

Modern WordPress uses a block-based editor.

Content can be assembled using blocks such as:

  • Paragraph

  • Heading

  • Image

  • List

  • Table

  • Columns

  • Buttons

  • Embed

The same block system can also be used by block themes to customize larger parts of the website.

A simple distinction is:

Theme = appearance

Plugin = functionality

For example:

Changing the visual layout → Theme

Adding ecommerce → Plugin

Adding an SEO sitemap → Plugin

Adding a contact form → Plugin

Keeping those responsibilities separate usually makes a WordPress site easier to maintain.

Choose niche → Install WordPress → Publish useful articles → Optimize internal structure → Acquire search traffic → Monetize

Possible monetization methods include:

  • Advertising

  • Affiliate marketing

  • Digital products

  • Services

  • Sponsorships

WordPress is particularly well suited to long-form content because content remains under the site owner's control.

Service page → Visitor arrives → Reads case study → Completes form → Business follows up

A business can combine WordPress with:

  • SEO

  • Google Ads

  • Email marketing

  • CRM systems

The website becomes a lead-generation asset rather than simply an online brochure.

Install WooCommerce → Add products → Configure payments → Configure shipping → Customer orders → Fulfill order

WordPress itself is not primarily an ecommerce system.

WooCommerce adds the ecommerce layer.

This combination gives merchants more infrastructure control than a fully hosted platform such as Shopify.

WordPress.org currently lists more than 71,000 free plugins.

That does not mean a site should install many of them.

Every plugin can potentially add:

  • Code

  • Database queries

  • Updates

  • Security exposure

  • Compatibility issues

Use the smallest plugin stack that solves the site's actual requirements.

Create a recoverable backup before:

  • WordPress updates

  • Major plugin updates

  • Theme changes

  • Server migrations

  • Significant code changes

WordPress documentation specifically recommends backing up before updating.

A backup is useful only if it can actually be restored.

Outdated components can create:

  • Security vulnerabilities

  • Compatibility problems

  • Bugs

WordPress can automatically install many minor and security updates.

Major changes should still be tested when the site is commercially important.

For important websites, test significant changes in a staging environment before applying them to the live site.

This is especially useful for:

  • WooCommerce stores

  • Membership sites

  • Custom plugins

  • Major theme changes

For example, running several caching plugins or multiple SEO systems can create conflicts and unnecessary complexity.

Choose one primary solution for each major function.

A simple blog and a busy ecommerce store do not need the same hosting.

As traffic increases, important resources can include:

  • CPU

  • Memory

  • Database performance

  • Caching

  • CDN

  • Backup capacity

Cheap hosting is not necessarily cheaper if performance problems begin affecting sales or traffic.

A major advantage of self-hosted WordPress is portability.

Maintain control of:

  • Domain account

  • Website files

  • Database backups

This reduces dependence on one developer or hosting company.

WordPress began as a publishing system and remains particularly strong for content-heavy websites.

Businesses can combine content with:

  • SEO

  • Affiliate marketing

  • Advertising

  • Newsletter acquisition

  • Digital products

Service businesses can use WordPress for:

  • Landing pages

  • Portfolio pages

  • Case studies

  • Lead generation

  • Booking

This can support businesses ranging from local services to agencies and professional consulting.

WooCommerce can turn WordPress into an online store.

This can support:

  • Physical products

  • Digital products

  • Subscriptions

  • Memberships

The additional flexibility also creates more maintenance responsibility than a fully hosted ecommerce system.

WordPress itself can also be used as the basis of a service business.

Freelancers can sell:

  • Website creation

  • Theme customization

  • WooCommerce setup

  • Site migration

  • Maintenance

  • Performance optimization

This fits naturally with Freelancing and Web Design.

WordPress has a large plugin ecosystem for connecting external services.

Common integration categories include:

  • Analytics

  • Email marketing

  • CRM

  • Payments

  • Ecommerce

  • SEO

  • Forms

  • Automation

  • Social media

For standard business requirements, a maintained plugin is usually easier than building a custom integration.

When no appropriate plugin exists, WordPress also provides APIs for custom development.

WordPress includes a REST API that allows external applications to interact with site data using JSON.

Standard endpoints can expose resources such as:

  • Posts

  • Pages

  • Categories

  • Tags

  • Media

  • Users

For example, an external application can retrieve WordPress posts through the API and display them in a separate frontend.

A custom architecture might look like:

WordPress CMS → REST API → Custom frontend

This allows WordPress to operate as a headless content-management backend.

Most ordinary business websites do not need this architecture.

Use standard WordPress rendering unless a custom frontend provides a meaningful benefit.

Developers can create their own:

  • Themes

  • Plugins

  • Custom post types

  • Taxonomies

  • API integrations

WordPress can therefore be extended beyond conventional websites.

The tradeoff is maintenance.

Custom code must continue working as WordPress, PHP, themes, and plugins evolve.

The core software costs nothing, but hosting, domains, premium plugins, development, and maintenance can create meaningful expenses.

A self-hosted WordPress website requires ongoing attention to:

  • Updates

  • Security

  • Backups

  • Hosting

  • Plugin compatibility

A managed platform handles more of this automatically.

Plugins and themes are developed by many different organizations and developers.

Two individually functional plugins can still conflict when installed together.

Test important updates.

Installing optimization plugins cannot completely compensate for severely inadequate hosting.

Infrastructure still matters.

Custom code can solve unusual business requirements but can also make future upgrades harder.

Prefer standard WordPress capabilities and maintained plugins when they solve the problem adequately.

WordPress security is not determined only by WordPress core.

The full environment includes:

  • Hosting

  • Plugins

  • Themes

  • Administrator accounts

  • Passwords

  • Server configuration

Unused plugins and themes should not remain installed indefinitely.

Platform

Best Fit

Main Difference

WordPress

Content-heavy and highly customizable websites

Open source and self-hosted

Webflow

Visual website building with managed hosting

More integrated visual design workflow

Shopify

Dedicated ecommerce stores

Commerce infrastructure included

Custom development

Unique applications and workflows

Maximum flexibility with much higher development burden

Choose WordPress when:

  • Content publishing matters

  • You want control over hosting

  • You need a large plugin ecosystem

  • Customization is important

  • You want to avoid dependence on one hosted website builder

Choose Webflow when visual site building and managed infrastructure are more important than WordPress's plugin ecosystem.

Choose Shopify when ecommerce is the primary requirement and you prefer a more managed commerce platform.

Choose custom development when the product behaves more like a software application than a conventional content website.

Yes.

The open-source WordPress software available from WordPress.org is free and licensed under the GPL.

Hosting, domains, premium plugins, and other services can still cost money.

WordPress.org provides the open-source WordPress software for self-hosting.

WordPress.com is a hosted service built around WordPress with its own pricing plans and infrastructure.

For self-hosted WordPress.org, yes.

You need a server or hosting provider capable of running WordPress.

No for many standard websites.

Themes, blocks, and plugins allow users to build substantial websites without writing code.

Coding becomes useful for advanced customization and custom integrations.

Yes.

WooCommerce is a widely used WordPress ecommerce plugin that adds products, checkout, orders, payments, and other store functionality.

Yes, particularly when the business values content publishing, extensibility, ownership, and control.

The tradeoff is greater maintenance responsibility compared with a fully managed website builder.

Canonical Markdown
1WordPress is an open-source content management system used to build websites, blogs, online stores, membership sites, directories, publications, and other web-based businesses.
2
3The WordPress software itself is free, but a self-hosted WordPress website normally requires separate hosting and a domain. Its main advantage is flexibility: themes and plugins can turn the same core system into anything from a simple blog to an e-commerce store or custom web application.
4
5# Quick Facts
6
7
8| Item | Details |
9| --------------- | ----------------------------------------------------------------------- |
10| Main use | Building and managing websites |
11| Best for | Blogs, business websites, content sites, ecommerce, and custom websites |
12| Core software | Free and open source |
13| License | GPLv2 or later |
14| Hosting | Required separately for self-hosted WordPress |
15| Domain | Required separately for a custom site |
16| Website share | More than 43% of the web according to WordPress.org |
17| Free plugins | 71,000+ in the official directory |
18| Themes | Thousands of free and commercial options |
19| Ecommerce | Available through plugins such as WooCommerce |
20| API | Built-in REST API |
21| Coding required | No for basic sites; useful for advanced customization |
22
23
24# Pricing
25
26The WordPress software available from WordPress.org is free.
27
28There is no WordPress.org subscription fee or per-transaction platform fee for using the core software commercially.
29
30A realistic self-hosted WordPress site can still involve costs for:
31
32- Domain registration
33- Web hosting
34- Premium themes
35- Premium plugins
36- Backups
37- Email services
38- Development
39- Maintenance
40
41The practical cost depends more on the website's hosting and plugin stack than on WordPress itself.
42
43## WordPress.org vs WordPress.com
44
45These are related but different services.
46
47**WordPress.org** provides the open-source WordPress software that can be installed on your own hosting.
48
49**WordPress.com** is a hosted service with its own free and paid plans.
50
51A typical self-hosted setup is:
52
53Domain → Hosting → Install WordPress → Choose theme → Add plugins → Publish site
54
55A WordPress.com setup is:
56
57Create WordPress.com account → Choose hosted plan → Build site
58
59For businesses that want maximum control over hosting, plugins, data, and customization, self-hosted WordPress is usually the more relevant version.
60
61# What It Does
62
63WordPress provides the underlying system for managing:
64
65- Pages
66- Posts
67- Images and media
68- Users
69- Categories
70- Tags
71- Navigation
72- Themes
73- Plugins
74
75A normal content workflow looks like:
76
77Create article → Add images → Choose categories → Publish → Search engines crawl page → Update article later
78
79Plugins can extend this into more specialized workflows.
80
81For example:
82
83WordPress → WooCommerce → Products → Checkout → Orders
84
85or:
86
87WordPress → Membership plugin → Paid member → Restricted content
88
89or:
90
91WordPress → Form plugin → Lead submission → CRM
92
93This extensibility is one of the main reasons WordPress can support many different business models.
94
95# Getting Started
96
97## 1. Buy a Domain
98
99Choose a domain that the business controls independently.
100
101Keeping the domain separate from the website software makes it easier to change hosting providers later.
102
103## 2. Choose WordPress Hosting
104
105A host needs to provide a server environment capable of running WordPress.
106
107WordPress currently recommends:
108
109- PHP 8.3 or greater
110- MariaDB 10.11 or greater, or MySQL 8.0 or greater
111- HTTPS support
112
113Apache or Nginx is recommended, although WordPress can run on other compatible web servers.
114
115For a beginner, managed WordPress hosting can reduce setup and maintenance work.
116
117## 3. Install WordPress
118
119Many hosting providers provide one-click installation.
120
121After installation, the main administrative interface is commonly accessed through:
122
123`yourdomain.com/wp-admin/`
124
125From there, the site owner manages content, plugins, themes, users, and settings.
126
127## 4. Choose a Theme
128
129A theme controls the site's presentation.
130
131It can determine:
132
133- Typography
134- Colors
135- Header
136- Footer
137- Page layouts
138- Blog layouts
139- Responsive behavior
140
141Start with a lightweight theme that already supports the required layout.
142
143Do not choose a theme simply because its demo contains many visual effects.
144
145## 5. Install Only Essential Plugins
146
147Plugins extend WordPress functionality.
148
149Examples include:
150
151- SEO
152- Forms
153- Ecommerce
154- Security
155- Caching
156- Backups
157- Memberships
158- Analytics
159
160Install plugins because the site needs a specific capability, not because a plugin appears useful.
161
162## 6. Create Core Pages
163
164A business website commonly begins with pages such as:
165
166- Home
167- About
168- Services or Products
169- Contact
170- Privacy Policy
171
172Content-driven websites can then add articles through WordPress Posts.
173
174# How to Use
175
176## Pages vs Posts
177
178WordPress separates more permanent content from chronological content.
179
180**Pages** are typically used for:
181
182- About
183- Services
184- Contact
185- Landing pages
186
187**Posts** are normally used for:
188
189- Articles
190- News
191- Tutorials
192- Blog content
193
194For a [Blogging](https://incomewiki.com/wiki/blogging) business, Posts usually make up most of the content library.
195
196## Block Editor
197
198Modern WordPress uses a block-based editor.
199
200Content can be assembled using blocks such as:
201
202- Paragraph
203- Heading
204- Image
205- List
206- Table
207- Columns
208- Buttons
209- Embed
210
211The same block system can also be used by block themes to customize larger parts of the website.
212
213## Themes and Plugins
214
215A simple distinction is:
216
217**Theme = appearance**
218
219**Plugin = functionality**
220
221For example:
222
223Changing the visual layout → Theme
224
225Adding ecommerce → Plugin
226
227Adding an SEO sitemap → Plugin
228
229Adding a contact form → Plugin
230
231Keeping those responsibilities separate usually makes a WordPress site easier to maintain.
232
233# Practical Workflows
234
235## Content Website
236
237Choose niche → Install WordPress → Publish useful articles → Optimize internal structure → Acquire search traffic → Monetize
238
239Possible monetization methods include:
240
241- Advertising
242- Affiliate marketing
243- Digital products
244- Services
245- Sponsorships
246
247WordPress is particularly well suited to long-form content because content remains under the site owner's control.
248
249## Business Lead Generation
250
251Service page → Visitor arrives → Reads case study → Completes form → Business follows up
252
253A business can combine WordPress with:
254
255- SEO
256- Google Ads
257- Email marketing
258- CRM systems
259
260The website becomes a lead-generation asset rather than simply an online brochure.
261
262## Ecommerce
263
264Install [WooCommerce](https://incomewiki.com/wiki/woocommerce) → Add products → Configure payments → Configure shipping → Customer orders → Fulfill order
265
266WordPress itself is not primarily an ecommerce system.
267
268WooCommerce adds the ecommerce layer.
269
270This combination gives merchants more infrastructure control than a fully hosted platform such as [Shopify](https://incomewiki.com/wiki/shopify).
271
272# Tips & Best Practices
273
274## Keep the Plugin Stack Small
275
276WordPress.org currently lists more than 71,000 free plugins.
277
278That does not mean a site should install many of them.
279
280Every plugin can potentially add:
281
282- Code
283- Database queries
284- Updates
285- Security exposure
286- Compatibility issues
287
288Use the smallest plugin stack that solves the site's actual requirements.
289
290## Back Up Before Major Changes
291
292Create a recoverable backup before:
293
294- WordPress updates
295- Major plugin updates
296- Theme changes
297- Server migrations
298- Significant code changes
299
300WordPress documentation specifically recommends backing up before updating.
301
302A backup is useful only if it can actually be restored.
303
304## Keep WordPress, Plugins, and Themes Updated
305
306Outdated components can create:
307
308- Security vulnerabilities
309- Compatibility problems
310- Bugs
311
312WordPress can automatically install many minor and security updates.
313
314Major changes should still be tested when the site is commercially important.
315
316## Avoid Editing Production Sites Blindly
317
318For important websites, test significant changes in a staging environment before applying them to the live site.
319
320This is especially useful for:
321
322- WooCommerce stores
323- Membership sites
324- Custom plugins
325- Major theme changes
326
327## Do Not Install Multiple Plugins for the Same Job
328
329For example, running several caching plugins or multiple SEO systems can create conflicts and unnecessary complexity.
330
331Choose one primary solution for each major function.
332
333## Choose Hosting Based on Workload
334
335A simple blog and a busy ecommerce store do not need the same hosting.
336
337As traffic increases, important resources can include:
338
339- CPU
340- Memory
341- Database performance
342- Caching
343- CDN
344- Backup capacity
345
346Cheap hosting is not necessarily cheaper if performance problems begin affecting sales or traffic.
347
348## Control the Domain and Backups
349
350A major advantage of self-hosted WordPress is portability.
351
352Maintain control of:
353
354- Domain account
355- Website files
356- Database backups
357
358This reduces dependence on one developer or hosting company.
359
360# Business Uses
361
362## Blogging and Publishing
363
364WordPress began as a publishing system and remains particularly strong for content-heavy websites.
365
366Businesses can combine content with:
367
368- SEO
369- Affiliate marketing
370- Advertising
371- Newsletter acquisition
372- Digital products
373
374## Business Websites
375
376Service businesses can use WordPress for:
377
378- Landing pages
379- Portfolio pages
380- Case studies
381- Lead generation
382- Booking
383
384This can support businesses ranging from local services to agencies and professional consulting.
385
386## Ecommerce
387
388WooCommerce can turn WordPress into an online store.
389
390This can support:
391
392- Physical products
393- Digital products
394- Subscriptions
395- Memberships
396
397The additional flexibility also creates more maintenance responsibility than a fully hosted ecommerce system.
398
399## Freelance Web Development
400
401WordPress itself can also be used as the basis of a service business.
402
403Freelancers can sell:
404
405- Website creation
406- Theme customization
407- WooCommerce setup
408- Site migration
409- Maintenance
410- Performance optimization
411
412This fits naturally with [Freelancing](https://incomewiki.com/wiki/freelancing) and [Web Design](https://incomewiki.com/wiki/web-design).
413
414# Integrations
415
416WordPress has a large plugin ecosystem for connecting external services.
417
418Common integration categories include:
419
420- Analytics
421- Email marketing
422- CRM
423- Payments
424- Ecommerce
425- SEO
426- Forms
427- Automation
428- Social media
429
430For standard business requirements, a maintained plugin is usually easier than building a custom integration.
431
432When no appropriate plugin exists, WordPress also provides APIs for custom development.
433
434# Advanced Use
435
436## REST API
437
438WordPress includes a REST API that allows external applications to interact with site data using JSON.
439
440Standard endpoints can expose resources such as:
441
442- Posts
443- Pages
444- Categories
445- Tags
446- Media
447- Users
448
449For example, an external application can retrieve WordPress posts through the API and display them in a separate frontend.
450
451A custom architecture might look like:
452
453WordPress CMS → REST API → Custom frontend
454
455This allows WordPress to operate as a headless content-management backend.
456
457Most ordinary business websites do not need this architecture.
458
459Use standard WordPress rendering unless a custom frontend provides a meaningful benefit.
460
461## Custom Themes and Plugins
462
463Developers can create their own:
464
465- Themes
466- Plugins
467- Custom post types
468- Taxonomies
469- API integrations
470
471WordPress can therefore be extended beyond conventional websites.
472
473The tradeoff is maintenance.
474
475Custom code must continue working as WordPress, PHP, themes, and plugins evolve.
476
477# Limitations & Common Mistakes
478
479## Free Software Does Not Mean Free Website
480
481The core software costs nothing, but hosting, domains, premium plugins, development, and maintenance can create meaningful expenses.
482
483## Maintenance Is the Owner's Responsibility
484
485A self-hosted WordPress website requires ongoing attention to:
486
487- Updates
488- Security
489- Backups
490- Hosting
491- Plugin compatibility
492
493A managed platform handles more of this automatically.
494
495## Plugin Conflicts Can Occur
496
497Plugins and themes are developed by many different organizations and developers.
498
499Two individually functional plugins can still conflict when installed together.
500
501Test important updates.
502
503## Poor Hosting Can Hurt Performance
504
505Installing optimization plugins cannot completely compensate for severely inadequate hosting.
506
507Infrastructure still matters.
508
509## Excessive Customization Creates Technical Debt
510
511Custom code can solve unusual business requirements but can also make future upgrades harder.
512
513Prefer standard WordPress capabilities and maintained plugins when they solve the problem adequately.
514
515## Security Depends on the Entire Stack
516
517WordPress security is not determined only by WordPress core.
518
519The full environment includes:
520
521- Hosting
522- Plugins
523- Themes
524- Administrator accounts
525- Passwords
526- Server configuration
527
528Unused plugins and themes should not remain installed indefinitely.
529
530# Alternatives
531
532
533| Platform | Best Fit | Main Difference |
534| ------------------ | ---------------------------------------------- | ------------------------------------------------------- |
535| WordPress | Content-heavy and highly customizable websites | Open source and self-hosted |
536| Webflow | Visual website building with managed hosting | More integrated visual design workflow |
537| Shopify | Dedicated ecommerce stores | Commerce infrastructure included |
538| Custom development | Unique applications and workflows | Maximum flexibility with much higher development burden |
539
540
541Choose WordPress when:
542
543- Content publishing matters
544- You want control over hosting
545- You need a large plugin ecosystem
546- Customization is important
547- You want to avoid dependence on one hosted website builder
548
549Choose Webflow when visual site building and managed infrastructure are more important than WordPress's plugin ecosystem.
550
551Choose [Shopify](https://incomewiki.com/wiki/shopify) when ecommerce is the primary requirement and you prefer a more managed commerce platform.
552
553Choose custom development when the product behaves more like a software application than a conventional content website.
554
555# FAQ
556
557## Is WordPress free?
558
559Yes.
560
561The open-source WordPress software available from WordPress.org is free and licensed under the GPL.
562
563Hosting, domains, premium plugins, and other services can still cost money.
564
565## What is the difference between WordPress.org and WordPress.com?
566
567WordPress.org provides the open-source WordPress software for self-hosting.
568
569WordPress.com is a hosted service built around WordPress with its own pricing plans and infrastructure.
570
571## Do I need hosting for WordPress?
572
573For self-hosted WordPress.org, yes.
574
575You need a server or hosting provider capable of running WordPress.
576
577## Do I need coding skills?
578
579No for many standard websites.
580
581Themes, blocks, and plugins allow users to build substantial websites without writing code.
582
583Coding becomes useful for advanced customization and custom integrations.
584
585## Can WordPress run an online store?
586
587Yes.
588
589WooCommerce is a widely used WordPress ecommerce plugin that adds products, checkout, orders, payments, and other store functionality.
590
591## Is WordPress good for business websites?
592
593Yes, particularly when the business values content publishing, extensibility, ownership, and control.
594
595The tradeoff is greater maintenance responsibility compared with a fully managed website builder.
596
597# Sources
598
599- [WordPress.org — About WordPress](https://wordpress.org/about/)
600- [WordPress.org — Features](https://wordpress.org/about/features/)
601- [WordPress.org — Download WordPress](https://wordpress.org/download/)
602- [WordPress.org — Requirements](https://wordpress.org/about/requirements/)
603- [WordPress.org — Plugins](https://wordpress.org/plugins/)
604- [WordPress.org — Themes](https://wordpress.org/themes/)
605- [WordPress.org Documentation — Introduction to Plugins](https://wordpress.org/documentation/article/introduction-to-plugins/)
606- [WordPress.org Documentation — Updating WordPress](https://wordpress.org/documentation/article/updating-wordpress/)
607- [WordPress Developer Resources — REST API Handbook](https://developer.wordpress.org/rest-api/)
608- [WordPress Developer Resources — REST API Reference](https://developer.wordpress.org/rest-api/reference/)
609- [WordPress Developer Resources — What Is a Theme?](https://developer.wordpress.org/themes/getting-started/what-is-a-theme/)
610- [WordPress.com — Pricing](https://wordpress.com/pricing/)