0.1What is WordPress? (.org vs .com)
The essentials in 30 seconds
- WordPress is a CMS: software that lets you create and manage a site (pages, posts, media, menus) without coding. It powers more than 4 out of 10 sites worldwide.
- WordPress.org = the free software you install with a hosting provider: total freedom (themes, plugins, code, e-commerce).
- WordPress.com = a turnkey hosted service, simpler but restricted depending on the plan. This guide covers .org.
Running mini-case — Samir and the Atelier Bahja
Samir is a WordPress freelancer in Casablanca. Hassan, a ceramist, asks him for a site to present his collections, publish care advice and, later, sell a few pieces online. Samir must first explain simply what WordPress is and why he will not work on WordPress.com: Hassan needs a shop, a blog and full control over the design. This is the starting point for the whole guide.
We follow Samir and the Atelier Bahja from level 0 through to the WooCommerce shop at level 4.
1. A CMS for publishing without coding
A CMS (content management system) lets you create and manage a site from an interface: you write a post, upload a photo, arrange pages in a menu — without touching the code. WordPress is the most widely used CMS in the world, which guarantees a huge community, thousands of themes and plugins, and a highly sought-after skill on the market.
For Samir, the issue is concrete: Hassan must be able to publish himself a new collection or a care tip without calling a developer every week. WordPress meets exactly that need: a clear administration, a visual editor and user roles to limit permissions.
2. .org or .com?
WordPress.org is the free, open-source software. You download it and install it with a hosting provider: you control everything — themes, plugins, files, database, code. This is the professional route, essential as soon as you want a WooCommerce shop, a business plugin or a custom design.
WordPress.com is a service hosted by Automattic: you create a site in a few clicks, but the lower plans restrict plugins and themes, and may display ads. Fine for a personal blog, insufficient for Hassan's evolving site. Samir decides: self-hosted WordPress.org, as throughout this guide.
🔎 Concrete example — Answering Hassan in three arguments (Samir case)
Hassan's needs: showcase site + blog + small shop.
Argument 1: WordPress.org allows WooCommerce (shop) with no plan limit.
Argument 2: Hassan will be able to publish his collections and advice himself.
Argument 3: the site and data stay with his hosting provider, not with a closed service.
→ Decision: self-hosted WordPress.org.Result: the client understands the technical choice without jargon.
Lesson: every argument is tied to a concrete client need.
Section vocabulary
- CMS
- Content management system: software for creating and managing a site (pages, posts, media) without coding.
Simple example: Hassan publishes a post on stoneware care from the administration.
What it is not: editing HTML files by hand for every new piece of content.
Reflex: “I publish from an interface” = CMS.
- WordPress.org
- The free, open-source software, installed with your hosting provider: total control of the site.
Simple example: Samir installs WordPress.org with the hosting provider chosen for the Atelier Bahja.
What it is not: confusing .org with a turnkey hosting service.
Reflex: .org = software you install.
- WordPress.com
- Turnkey hosted service: simple, but plugins and themes are restricted depending on the plan.
Simple example: a personal blog can make do with .com; Hassan's shop cannot.
What it is not: believing .com offers the same freedoms as .org.
Reflex: .com = a service, not the free software.
- Open source
- Free, modifiable code, supported by a large community.
Simple example: Samir can adapt a theme or plugin to Hassan's needs.
What it is not: paying a licence to use the WordPress core.
Reflex: WordPress.org is free and sustainable.
- Theme / plugin
- The theme defines appearance; the plugin adds features.
Simple example: a theme for the workshop's style, WooCommerce for the shop.
What it is not: looking for a feature in a theme when it belongs to a plugin.
Reflex: appearance = theme; feature = plugin.
In practice — Choosing .org or .com for a project
- List the client's needs: blog, shop, form, member area, custom design.
- For each need, ask yourself whether it requires plugins or code (→ .org) or fits in a simple service (→ .com).
- Check the budget: hosting and domain for .org; subscription for .com.
- Write the decision and one reason in a sentence, as Samir does with Hassan.
Ready-to-say script — explaining .org/.com to the client (30s)
“WordPress comes in two forms. The free version you install with your hosting provider is the one that allows the shop and a custom design: the site belongs to you. The other is a ready-made service, simpler but limited. For your workshop, we will go with the full version.”
Avoid acronyms; talk about “what the site will be able to do” rather than technical details.
Copy-paste template — .org / .com decision
PROJECT: _______________
NEEDS: blog / shop / form / members / custom
NEEDS REQUIRING PLUGINS: _______________
NEEDS THAT FIT IN A SIMPLE SERVICE: _______________
DECISION (.org / .com): _______________
ONE-SENTENCE REASON: _______________Personal blog
A free .com may be enough if you accept the limits and the absence of a shop.
Showcase site
.org with shared hosting: inexpensive and fully customisable.
Online shop
WooCommerce requires .org: proper hosting, SSL and backups.
Client with limited technical skills
Plan a short administration training so they can publish alone without breaking the layout.
✓ Best practices
- Start from the client's needs, not the technology.
- Reserve .com for simple, closed projects.
- Explain ownership of the site and data.
✗ Common pitfalls
- Confusing .org and .com because the name is the same.
- Promising a shop on a restricted .com plan.
- Choosing .org without planning for hosting and backups.
Key takeaways
- WordPress is a CMS: you publish without coding.
- .org = free software installed with a hosting provider, total control.
- .com = simple but restricted hosted service.
- Theme = appearance; plugin = feature.
48h Challenge — apply tomorrow
Take a real or fictional project: list its needs (blog, shop, form) and write in three sentences why you choose WordPress.org. Compare with what a .com service would allow. 15 minutes.
- I can explain what a CMS is.
- I distinguish WordPress.org from WordPress.com based on facts.
- I can justify choosing self-hosted for a project.
Frequently asked questions
Isn't WordPress.com simpler to get started with?
Simpler at first, but you quickly hit its limits: restricted free plugins, no shop on the lower plans, ads. WordPress.org requires an installation, but it has become trivial (section 0.3) and offers the freedom that makes the CMS worthwhile.
Do you need to know how to code to use WordPress?
No, for the vast majority of uses: the interface, themes and plugins are enough to create a complete site. Code (CSS, PHP) only comes into play for fine customisation or bespoke work, at levels 4 and 5, and remains optional.
Does the site really belong to me with WordPress.org?
Yes: the files and database are with your hosting provider, under your account. You can export, back up and migrate the site whenever you want, without depending on a closed platform.
Samir must explain to Hassan why he proposes self-hosted WordPress.org rather than WordPress.com. Which argument is the most accurate?