Latest / No Stress Web Success / Web Understood: Why HTML + Tailwind Beats WordPress for Small Sites | 12
Transcript
- 0:00What if I told you that for a huge number of websites, portfolios,
- 0:04small business sites, landing pages, even many blogs,
- 0:09the fastest, cheapest, most secure, and easiest to maintain option is just HTML plus CSS.
- 0:17No WordPress, no plugins, no database.
- 0:21Today, we're talking about when a pure static site, especially one built with
- 0:26Tailwind CSS, is actually the smarter move.
- 0:30And how to handle the one thing people always worry about, a working contact form.
- 0:35Welcome back. I'm Lisa Bowers, founder of 5Penny Web Studio,
- 0:40and this is No Stress Web Success.
- 0:43Today, we're comparing two very different ways of building a website.
- 0:47On one side, WordPress, the giant that powers a huge chunk of the web.
- 0:52On the other, a site built strictly with HTML plus CSS, often using a utility-first
- 0:59framework like Tailwind CSS.
- 1:02We'll cover the real advantages of the simple approach, when it clearly wins,
- 1:07and practical ways to get a contact form working without turning your site into
- 1:11a maintenance nightmare.
- 1:14What we mean by strictly HTML plus CSS, I mean a static website.
- 1:20The pages are just files.
- 1:22HTML for your structure, CSS for styling.
- 1:26There's no PHP language, no MySQL database, no server-side code running on every page load.
- 1:34You can still use a little JavaScript if you need interactivity, but the core is static.
- 1:40Tailwind makes this especially pleasant because you style directly in your markup.
- 1:44With utility classes instead of writing endless custom CSS.
- 1:49You can hand code it, or you can use a static generator like Astro,
- 1:54or even just a folder of HTML files.
- 1:57The key point is there's no CMS database, no plugin ecosystem,
- 2:03and no constant updates for security.
- 2:06So let's be concrete about the advantages. Speed and performance.
- 2:10A pure HTML plus CSS site is almost always faster.
- 2:15There's no database queries, no PHP rendering, and no plugin overhead.
- 2:21You get a near-perfect lighthouse score with almost no effort.
- 2:25Security There's almost nothing to hack. No login pages, no outdated plugins, no database.
- 2:32Static files are extremely hard to compromise compared to a typical WordPress install.
- 2:38Cost Hosting can be free or low cost.
- 2:42Options like GitHub pages and Cloudflare pages provide options.
- 2:47There's no monthly managed WordPress hosting bill.
- 2:51Maintenance. Again, no updates. Your site is not broken after the latest update panic.
- 2:59You change a file and redeploy.
- 3:02Simplicity and control. You own every line. No mysterious theme settings, no plug-in conflicts.
- 3:09Tailwind keeps the CSS disciplined and consistent.
- 3:14Lastly, longevity. A static file from 2015 generally still works the same way today.
- 3:21WordPress sites often need ongoing attention just to stay online and secure.
- 3:26Now, don't misunderstand me. WordPress is powerful when you need a real CMS.
- 3:32Frequent content changes by non-technical people, memberships,
- 3:36e-commerce, complex editorial workflows.
- 3:39For many other sites, that power is overkill, and it comes with real cost and
- 3:44performance, security, and time.
- 3:49So, when should you choose the simple route?
- 3:52Maybe you're developing a portfolio or personal website, a business brochure
- 3:58or service site, marketing sites with individual landing pages,
- 4:03sites that change very rarely,
- 4:07Projects where you or a developer are comfortable editing HTML.
- 4:12Basically, anything where speed, security, and low ongoing costs matter more
- 4:18than a visual editor for non-technical editors.
- 4:22If the content really changes, or if the people updating it can handle the markdown
- 4:28of basic HTML, then static wins.
- 4:31If you need a non-technical teen publishing daily blog post and you need categories
- 4:37and tags and media libraries, then WordPress or another CMS is usually the better tool.
- 4:43The decision is less about which is better in absolute terms and more about
- 4:49which matches your actual job.
- 4:53So let's talk about contact forms. The classic objection is,
- 4:58but how do I get a contact form working without a back end?
- 5:02The good news is you have solid, low-maintenance options.
- 5:07With WordPress, you're used to installing a plugin, Gravity Forms or Fluent
- 5:13Forms, and it's set it to go.
- 5:16With our HTML site, it's still not difficult. You just need that developer building it into your website.
- 5:23And to include it with your initial project.
- 5:25So, forms, backend services. This is option one, and it's your easiest option.
- 5:32These are services that give you an endpoint. You point a normal HTML form at
- 5:37their URL, and they handle everything in the backend for you.
- 5:41The email, the spam protection, and the storage.
- 5:45There's several options out there that are very popular. WIP,
- 5:49three forms, FormSpark, FormSpree, And all these forms, services provide you
- 5:56different options, different tiers.
- 5:59It really depends on your volume and what other extras you might need with it.
- 6:05Mostly, they'll provide the spam filtering, the email notifications.
- 6:09Some may even give you a simple dashboard. There's no server code required.
- 6:14The second option is the serverless function. And this is basically a tiny function
- 6:20written in Node or Python that receives the form post, validates it,
- 6:25and sends the email for you using an API key.
- 6:29You deploy it on the same platform as your website, and it's still almost zero
- 6:33maintenance once it's set up.
- 6:36Now, the thing to consider is...
- 6:39You're trying to do this under any kind of certain regulations or requirements,
- 6:44to how you keep or store your user data.
- 6:48All your forms are collecting PII, so you need to take this into consideration
- 6:53when you look at your options or what vendor you may choose to go with.
- 6:57Don't be shy about asking your vendors for their data and retention policies.
- 7:02Any reputable provider will be willing to answer those questions for you.
- 7:07For security, spam is the main ongoing concern.
- 7:11The form services handle most of it with honeypots and rate limits and even
- 7:16provide captures for you, so you really need to write your own spam logic.
- 7:21At the end of the day, it's fairly simple. You just have to get the right people
- 7:26involved and choose the right partners.
- 7:30So let's wind this down. Pure HTML plus CSS gives you speed,
- 7:36security, low cost, and almost no maintenance.
- 7:40It's the better choice when your content doesn't need a full CMS.
- 7:45Contact forms are a solved problem using a form service or a tiny serverless function.
- 7:52You don't need WordPress or any other CMS just to collect messages from your visitors.
- 7:57If you're building a site that mostly sits there looking good and occasionally
- 8:02needs a contact form, start simple.
- 8:05You can always add complexity later.
- 8:08Complexity is easy to add, but it's very hard to remove.
- 8:13That being said, thanks for joining us today I hope you'll come back next Wednesday
- 8:18for episode 13 Part of our Accessibility for Humans series Where we continue
- 8:23to talk about the WCAG rules on color,
- 8:26In the meantime, if you have questions or something you're struggling with on
- 8:30your own website Reach out to 5pennyweb.com We'll be happy to talk to you,
- 8:35If you found this episode helpful, please leave us a review so that other non-profit
- 8:40and small teams can find us.
- 8:43Again, I will see you next week.