Easy Newsletter Builder documentation

Build the newsletter. Understand every step.

This guide covers Lite and Pro in plain language: installation, building, previewing, moving the finished HTML into your sending platform, team tools, and common fixes.

01

Start here: what Easy Newsletter Builder does

Easy Newsletter Builder is a creation workspace. It gives you a consistent newsletter structure, guided content areas, rich editing, image controls, live preview, and finished HTML.

Your email platform still handles contacts, lists, delivery, scheduling, reporting, unsubscribe processing, and campaign management. This separation is intentional: ENB focuses on making the newsletter easier to build.

Choose Lite if...

You want the simplest complete workflow.

Lite is ideal for one saved newsletter, a solo site owner, occasional updates, or your first consistent newsletter.

Learn about Lite

Choose Pro if...

You publish regularly or work with other people.

Pro adds multiple issues, a private front-end portal, deeper permissions, collaboration, recovery, and workflow tools.

Learn about Pro

02

Install Easy Newsletter Builder Lite

  1. 1

    Open Plugins

    In your WordPress site, go to Plugins → Add New.

  2. 2

    Find the plugin

    Search for “Easy Newsletter Builder.”

  3. 3

    Install and activate

    Select Install Now, then Activate.

  4. 4

    Open the workspace

    Choose Easy Newsletter from the admin menu.

03

Build your first newsletter

Keep the first test short. The goal is to learn the flow before you build a full public issue.

  1. Open Easy Newsletter and start blank or load the sample.
  2. Add the newsletter title, volume or issue, date, and inbox preview text.
  3. Write a short Hero / Masthead headline and introduction.
  4. Add one Featured Update — the item readers should notice first.
  5. Add one or two Latest Updates or a useful Custom Section.
  6. Set one clear Final CTA and review the Footer Body.
  7. Hide any main block the issue does not need.
  8. Save, preview, and generate the finished newsletter HTML.
  9. Place the HTML into your sending platform and send yourself a test.

04

Understand the newsletter sections

Issue Details

Identifies the newsletter. Use a title, issue information, date, and inbox preview text that will still make sense when you look back at older issues.

Hero / Masthead

Opens the issue and sets the tone. A clear headline and a short introduction usually work better than a long wall of text.

Featured Update

Holds the most important story or announcement. Explain what happened, why it matters, and what the reader should do next.

Latest Updates

Adds shorter, focused items. Give each update a title that helps readers understand it while scanning.

Custom Sections

Adds flexible extra blocks for events, resources, sponsor notes, reminders, links, FAQs, or anything else the issue genuinely needs.

Final CTA

Ends with one clear next step. A focused closing action is stronger than several competing buttons.

Footer Body

Holds contact details, mailing information, and the subscription links or merge codes required by your sending platform.

Images

Choose an image from the Media Library or use a direct image URL. Select a display size that fits the image. Medium or Small often works better for tall images; Full width works well for broad banners.

Buttons and links

Use action-focused labels such as “Read the Update,” “Register Now,” or “Visit Support.” Set the button URL carefully, choose the new-tab option when appropriate, and test every link in a real email.

05

Preview and use the finished HTML

The browser preview shows the shape of the finished newsletter. Check the big picture first, then the details.

  • Is the main reason for the issue clear near the top?
  • Are unused sections hidden?
  • Are the images correctly sized and placed?
  • Do button labels explain what happens next?
  • Is the footer accurate and complete?

When the preview is ready, use the generated newsletter code in your sending platform's HTML or code-based editor. The exact screen varies by platform.

06

Use the sending platform you already trust

FluentCRM

  1. Build and preview the newsletter in ENB.
  2. Create a campaign or template in FluentCRM.
  3. Use FluentCRM's code-based email option.
  4. Place the ENB HTML into the editor.
  5. Verify SmartCodes and subscription links.
  6. Send a test, then send or schedule in FluentCRM.

Mailchimp, MailPoet, and others

  1. Choose the platform's HTML or code option.
  2. Place the finished ENB code into the editor.
  3. Add or verify the platform's merge tags and required links.
  4. Send a real test from that platform.

Some services adjust imported HTML or display a different editor preview. Trust the delivered test email more than the editor preview.

07

Pro setup and workflow

Install and activate Pro

  1. Purchase Pro and download the plugin ZIP from your order or account.
  2. Go to Plugins → Add New → Upload Plugin.
  3. Select the Pro ZIP, install it, and activate the plugin.
  4. Open the Pro settings and enter the license key from your purchase.
  5. Activate the license and confirm that its status is Active.

Private front-end portal

Pro can provide a private newsletter workspace on your website for approved, logged-in users. Enable or disable it from the Pro controls, then grant access by role or by a specific user. Individual permissions can control viewing, editing, marking ready for publishing, and archive management.

Multiple newsletters and status

Create and organize separate named issues, prepare future newsletters, archive completed work, and restore an archived issue when needed. Ready for Publish means the issue is finished inside ENB and ready for final testing in the sending platform. It does not send the email.

Team access and editing safety

Role-based and individual permissions decide who can view, edit, mark ready, archive, restore, or manage newsletter work. Builder locking helps prevent accidental overwrites. If an issue is already being edited, Knock Knock lets another user request access so the current editor can save and exit.

Autosaves, backups, and archives

Autosave and backup snapshots help protect longer editing sessions. They are a safety net, so save intentionally after meaningful changes and before leaving the workspace. Archives keep finished issues out of the active list without deleting them immediately.

Personal and shared macros

Save frequently used merge codes, sign-offs, support links, disclaimers, and recurring snippets. Use labels that will make sense later, and keep the exact code format required by the sending platform. FluentCRM SmartCodes are still processed by FluentCRM when the campaign is sent.

08

Troubleshooting

I do not see the Easy Newsletter menu.

Confirm that the plugin is activated. In Pro, also confirm that your role or individual account has the required access.

Pro says a license is required.

Open the Pro license settings, enter the key from your purchase, and activate it. If it still does not show Active, contact support with the exact message you see.

The email looks different in my sending platform.

Use the platform's code-based editor when available, then send a real test. Some services alter imported HTML or show an editor preview that differs from the delivered email.

Images are missing.

Confirm that the image still exists, its URL is publicly reachable, and the sending platform can access it. Avoid private or restricted image URLs.

Merge codes or SmartCodes did not work.

Merge codes are processed by the sending platform. Confirm the exact syntax, place them in the proper editor, and test them from that platform.

Another user appears stuck in the builder.

Ask the editor to save and exit. If they are unavailable, an administrator can use Pro's emergency unlock carefully.

09

Get useful support faster

When you contact support, please include:

  • Whether you use Lite or Pro
  • Your plugin version
  • Your sending platform
  • What you expected to happen
  • What actually happened
  • The exact error message and a screenshot, if helpful

Do not send passwords, private administrator credentials, or secret keys through normal email.