Skip to content
Tutorials Center
My learning

Topics

Lesson 8 of 68 ยท Using the Dashboard

Page Builders, Landing Pages, Forms and Choosing Plugins

Compare the block editor with page builders such as Elementor, build a landing page, pick a contact form and user plugin, and vet any plugin or theme with a checklist.

Not everyone who builds a WordPress site writes PHP. Many sites are assembled from a theme, a handful of plugins and a page builder: a visual tool for laying out pages by dragging blocks around. As a developer you will meet these sites constantly: clients bring them to you, and you need to know what a builder does to the HTML, the speed and the long-term cost of a site.

This lesson compares the built-in block editor with third-party page builders, explains the difference between plugins, themes and widgets, walks through creating a landing page and a contact form, and ends with a checklist for deciding whether a plugin is safe to install. The code is read-only except for two plain-PHP stand-ins that make the key ideas visible.

Three layers: theme, plugin, widget

A short reminder, because people confuse them (see also What Is WordPress?):

Theme Plugin Widget
Job Look and layout of the whole site Adds features (forms, SEO, shop, backups) Small piece of content in a widget area (sidebar, footer)
How many active One Many Many, per widget area
Survives a theme change? n/a Yes Areas may differ between themes
Examples Astra, Kadence, GeneratePress, Twenty Twenty-Five Yoast SEO, WooCommerce, Gravity Forms Search box, recent posts, social icons

A plugin can provide widgets (a plugin adds an "Upcoming events" widget) and blocks. Widgets are managed under Appearance > Widgets (or in the Site Editor for block themes); see Menus, Widgets and Sidebars. A sidebar is the region of a theme that holds widgets (not always at the side), commonly used for search, categories, recent posts, ads or a signup form.

Installing and activating

Plugins > Add New, search, Install Now, then Activate. Themes work the same way under Appearance > Themes. A downloaded ZIP can be installed with Upload Plugin. Deactivate a plugin you do not use and delete it: inactive code still sits on the server and can be attacked. Never install "nulled" (pirated) premium plugins; they are the most common source of hacked sites.

Customizing a theme without code

You can change a lot of a site's appearance without touching PHP:

  • Classic themes: Appearance > Customize opens the Customizer, a live preview with panels for Site Identity (title, logo, site icon), Colors, Menus, Widgets, Homepage Settings and Additional CSS.
  • Block themes: Appearance > Editor opens the Site Editor with templates, template parts, patterns and Styles (colors, typography, spacing and per-block styles; see Block Theme Basics).
  • Additional CSS accepts your own CSS rules, such as .site-title { letter-spacing: 0.05em; }. It is stored with the theme settings, applies on top of the theme's stylesheet and survives theme updates. Keep large amounts of CSS in a child theme instead (see Child Themes). A theme must be activated to show, and an unused theme should be deleted; keep one default theme as a fallback if your theme breaks.
  • To check a change on different devices use the Customizer's tablet and mobile preview icons.

The block editor versus page builders

Since WordPress 5.0 the core editor is the block editor (Gutenberg), and since 5.9 the Site Editor extends blocks to headers, footers and templates in block themes. Page builders existed first and are still very popular.

Block editor Page builder (Elementor, Divi, Beaver Builder, Bricks)
Included Yes, in core Plugin (free core, paid Pro)
Interface Writing-like, blocks in a column Visual canvas, drag widgets into sections, columns and rows
Design control Good, improving with each release Very detailed: spacing, animation, hover effects, responsive tweaks
Output Clean HTML in post_content Often a JSON structure in post meta plus much extra HTML and CSS
Speed Light Heavier (more DOM elements, scripts, CSS)
If you remove it Content stays The layout may be lost or turn into shortcodes

Why people choose builders: non-developers can build a complex layout quickly, reusable templates and section libraries are included, they have popups and forms, and visual editing is easy to demo to a client.

Why they hurt:

  • Lock-in. The layout lives in the builder's own format. Switching later means rebuilding pages.
  • Performance. Nested wrappers (section, column, widget container) make the page's HTML larger and slower, and builders load their CSS and JavaScript on every page.
  • Maintenance and cost. The builder is one more plugin to update, and pro licences renew yearly.
  • Quality of the markup. Accessibility and headings are only as good as the person using it.

The blocks route (a good block theme plus a pattern library, see Block Patterns) is the modern default; choose a page builder when the design needs it, the team already knows it, and you will keep paying attention to performance.

PHP Why a builder creates lock-in (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with fgets(STDIN)), it gets the next line from this box.

The builder's output turns into raw shortcode text when the plugin is gone; the block content is still readable HTML. A rescue script can recover the words but never the design. That is the practical meaning of lock-in.

Elementor in practice

Elementor is the most widely used page builder. The free version covers layout; Elementor Pro adds a theme builder (headers, footers, single post templates), forms, popups and dynamic content. Basic workflow:

  1. Plugins > Add New, search Elementor, Install and Activate.
  2. Create or open a page and click Edit with Elementor.
  3. The left panel lists widgets (heading, text, image, button, form...). Drag one onto the canvas, inside a container (the layout element that replaced the older section, column structure).
  4. Set content, typography, colour, spacing and responsive behaviour for desktop, tablet and mobile with the device icons at the bottom.
  5. Publish or Update. Use Settings to choose a page layout: Elementor Canvas (a blank page with no header or footer, ideal for landing pages), Elementor Full Width or the theme's default.

To keep the cost down: use few nested containers, compress images, disable features you do not use in Elementor > Settings > Features, and avoid dozens of animated widgets above the fold.

Landing pages

A landing page is a page designed for one purpose and one action: sign up, download, buy, register for an event. Visitors arrive from an ad, an email or a search result, so the page removes distractions.

Common types:

  • Lead generation (squeeze) page: a short pitch and a form to collect an email address.
  • Click-through page: warms the visitor up, then sends them to a checkout or signup page.
  • Event or webinar page, coming soon and thank-you pages.

Checklist for a landing page that converts:

  1. One clear headline that matches the ad or link that brought the visitor.
  2. One call to action (CTA) button, repeated, with an action verb ("Get the free guide").
  3. Benefits, proof (reviews, logos, numbers) and a short form with only the fields you need.
  4. A layout without the site menu and sidebar. Use the builder's canvas layout, a page template (see Template Hierarchy: you can create page-landing.php or choose a block template without a header), or a dedicated plugin such as SeedProd or the StarterTemplates library.
  5. Fast loading and mobile-first design. Every second of delay loses conversions.
  6. Tracking: a thank-you page or an event in your analytics tool, so you can measure results.

Contact forms

Almost every site needs a form. Popular plugins:

Plugin Notes
Contact Form 7 Free, minimal, developer friendly (forms are written as text tags)
WPForms Drag-and-drop builder, templates, beginner friendly
Gravity Forms Paid, very powerful (conditional logic, payments, add-ons)
Ninja Forms, Fluent Forms Builder style, free core with paid add-ons

Steps with a typical plugin: install and activate, create a form (name, email, message), configure the notification email, copy the shortcode ([contact-form-7 id="123"]) or insert the plugin's block, and test. Add a spam defence (honeypot field, reCAPTCHA or Turnstile) and a confirmation message. If emails do not arrive, the cause is usually that the server's mail() is blocked or flagged as spam: use an SMTP plugin with your email provider. To see how a form plugin works inside, build your own in Project: Contact Form Plugin, and for the security side read Forms and Nonces.

User and membership plugins

Core WordPress has users and roles (see Capabilities and Roles). For front-end features such as registration pages, profiles, directories, content restriction and paid memberships, people add a plugin. Examples: Ultimate Member and UsersWP (registration, login and profile pages), MemberPress (paid memberships and content protection), PeepSo (a social network). Check that the plugin keeps roles and capabilities in the standard system, not its own parallel one.

Choosing themes and plugins

Thousands of options exist, so use a checklist. The next stand-in turns it into code, which is a good way to think about it: a plugin passes only if all the red flags are absent.

PHP A plugin vetting checklist (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with fgets(STDIN)), it gets the next line from this box.

Use the same facts in the real plugin directory: active installations, last updated, tested up to, ratings and support forum are listed on every plugin's page. Also prefer plugins that do one job, check the performance cost (query monitor, page weight), keep the total number of plugins sensible (not a fixed limit, but every plugin is a maintenance and security liability), read the changelog, and run updates on a staging copy first. Look for a theme that is lightweight, updated, has good block or builder support and is accessible: Astra, Kadence, GeneratePress and the default Twenty Twenty-Five are common starting points. Heavy multipurpose themes with built-in sliders and shortcodes cause the same lock-in as builders.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What is the main long-term risk of building a whole site with a page builder?

    Builders store layouts in their own format. Block content is ordinary HTML and survives without extra plugins.
  2. 2. What distinguishes a plugin from a widget?

    A plugin extends functionality, and may provide widgets or blocks. A widget is a content item shown in a widget area.
  3. 3. Which page layout in Elementor is best for a landing page with no header or footer?

    Elementor Canvas renders only your content, without the theme's header, footer or sidebar.
  4. 4. Contact form emails never arrive. What is the most common fix?

    Servers often block or spam-flag PHP mail(); sending through SMTP authenticated with your mail provider is more reliable.
  5. 5. Which is a red flag when choosing a plugin?

    Abandoned plugins and known vulnerabilities are the main security risks; check update date, compatibility and support.

Summary

  • A theme sets the site's look, plugins add features and widgets place small content pieces in widget areas.
  • The block editor produces clean HTML; page builders such as Elementor give visual control at the cost of lock-in, weight and an extra dependency.
  • A landing page has one goal, one call to action and no distracting navigation; use a canvas layout or a page template.
  • Form plugins (Contact Form 7, WPForms, Gravity Forms) need spam protection and reliable SMTP mail.
  • Vet plugins by update date, compatibility, installs, support and vulnerabilities, and install only from official sources.
  • Deactivate and delete what you do not use, and update on a staging copy first.

Next: Backups, Updates and Maintenance.