CASE STUDY

An Online Book Store and Website: The Great Poop Book

We developed for Gal Alon, author of The Great Poop Book (thegreatpoopbook.com), a clean-code Laravel store that replaced a cluttered WordPress and WooCommerce site: the book at the centre, quick buy straight to payment, a secure hosted payment page, a full admin panel and a customer account area.

Gal Alon - The Great Poop Book
Books and humorous gifts
Store, admin panel, customer area
Nationwide delivery, self pickup in Ramat HaSharon
The home page of thegreatpoopbook.com: a humorous headline, the book illustration and the buy button
The home page · the book, the illustrations and the button, with no noise around them.
4Products instead of a crowded catalogue
2Payment providers, switchable in a click
9Designed email templates
5Ready popup designs
0External plugins to maintain

01. Background and challengeA cluttered WordPress site that hid the star: the book

The previous site was built on WordPress and WooCommerce, and over the years it had gathered many products, a permanent coupon strip at the top of the page, long texts at the bottom and a heavy preloader between pages. The book itself, the product people come for, got lost, and the main purchase button was a small text link.

Gal Alon's The Great Poop Book is a humour book that already sits in thousands of homes, and its website had to be as simple as it is: see the book, smile, buy. The challenge was to build a clean, fast site without losing what already worked.

The main challenges:

  • The book at the centre: a prominent buy button and a visible price instead of a small text link, and a page that leads to it without distractions.
  • The character of the book: the illustrations, the colours and the humorous tone had to stay and become the visual language of the whole site.
  • Existing search visibility: product URLs that already rank on Google had to be kept, and every URL that changed needed a redirect.
  • Payment that works from day one: secure payment, verification with the payment company and a test mode kept separate from live mode.
  • Shared hosting: an ordinary DirectAdmin server, with no dedicated server, no Composer and no terminal.

02. Our approachThe book at the centre, and everything else works for it

We started with design: we presented two versions of every page type (home, product, shop and checkout) and chose the clean direction together with the client. The book took centre stage with a prominent buy button, the range was cut to four products only (the book, the 5-accessories set, the toilet birthday set and the children's book), and the original illustrations became the visual language of the whole site.

Then we wrote the system itself in Laravel, in clean code and with no build step: plain CSS and JavaScript, a database installed by importing a single SQL file, and every sensitive setting, payment and mailing, editable from the admin panel rather than from the code.

Finally came deployment: uploading to the hosting, testing payment in test mode, switching to live mode and activating the redirects from the old URLs, so that the switch would be smooth for customers and for Google.

03. One product at the centreHow to build a store around a star product

When one product is the star, every page has to lead to it. That is why we built the store around as few steps as possible between wanting to buy and paying, and placed every extra where it helps rather than gets in the way.

  • Quick buy: a button on every product that goes straight to the payment page, without passing through a separate cart page.
  • Side cart: a drawer that opens without leaving the page, so the customer can keep browsing and adding.
  • A handwritten dedication: the customer writes a personal dedication and sees a preview in a handwriting font while typing.
  • A smart offer in the cart: the children's book at 50% off, right when the customer has already decided to buy.
  • Delivery as needed: home delivery, self pickup or direct delivery as a gift, and coupons for campaigns.

The decision to offer the extras inside the cart rather than on the home page is deliberate: on the home page they are noise, and in the cart, after the customer has already chosen, they are an offer that is easy to say yes to.

04. Payment, customers and securitySecure payment and bot-protected registration

Payment takes place on the payment company's secure hosted page: the customer goes there and returns to a thank-you page on the site. The site does not store card details and does not mark an order as paid until it verifies the payment directly with the payment company. The site owner chooses between Grow and iCredit, and between test and live mode, from the interface, and can test the connection with one click.

Registered customers get an account area with orders, saved addresses, details and password, and at checkout the details and address are pre-filled. So that registration does not become a target for bots, we built several layers of protection: a honeypot field, a time check, a calculation challenge and Turnstile, alongside a password policy with live feedback while typing and a limit on attempts for every form.

05. Shared hostingA full system installed without a terminal

The site is hosted on shared hosting running DirectAdmin: files are uploaded through the file manager and the database through phpMyAdmin, with no Composer and no terminal. This is a constraint that affects every decision, so the system was written to be installable without build tools: code that is ready to upload and a database installed by importing a single SQL file.

The settings that would normally need a configuration file, such as the payment provider, the working mode, sending email through Resend and the mailing details, are edited from the admin panel. The site owner changes them alone, without touching the server and without calling a developer for every change.

06. SEO and the move from WordPressA move that keeps what Google already knows

In a move from WordPress the first thing to check is the URLs. The product URLs were kept exactly as on the previous site, and every old URL that changed was given a 301 redirect to the matching page, so the existing rankings and links keep working.

On top of that came a sitemap, structured data for the product pages and commerce events for Google Analytics 4 and Meta, with Tag Manager and Search Console connected from the interface. There is no promise of ranking, but a sound structure, stable URLs and reliable measurement are the condition for competing and for understanding where sales come from.

The engines behind the project

Everything we built for The Great Poop Book, from the store the customer sees to the tools the site owner works with.

A design derived from the illustrations

An animated preloader built from the logo, and a shorter version on a return visit. An animated mobile menu and a store mega menu that opens on hover. A handwriting font, a yellow marker and the book illustrations on every page, fully adapted to mobile, tablet and desktop.

A fast buying experience

Quick buy from every product straight to the payment page, a side cart drawer, a handwritten dedication with a preview, a smart offer in the cart, coupons, home delivery, self pickup and direct delivery as a gift.

Payment on a secure hosted page

Connections to Grow and iCredit that you switch between in a click, test and live modes, a connection test from the interface and verification of the payment with the payment company before an order is marked as paid. The site does not store card details.

A full admin panel

Orders, products, coupons, users and pages in a tidy side menu. Editing of every heading and text on the site, including the emails. A popup builder with 5 designs, page targeting, frequency and dates, and internal reports with views, sales, a purchase funnel and period comparison.

Registered customers and security

An account area with orders, saved addresses, details and password, and pre-filled details at checkout. Bot protection at registration: a honeypot, a time check, a calculation challenge and Turnstile, a password policy and an attempt limit on every form.

Emails, measurement and SEO

9 designed email templates, from order confirmation to "your order is on its way", sent through Resend with a preview and a test send from the interface. Connection to Google Analytics 4, Tag Manager, Meta Pixel and Search Console, a sitemap, structured data and 301 redirects.

Instead of a WordPress site that needs plugins, updates and maintenance, The Great Poop Book now has a single clean-code system that the site owner runs alone: changing texts, launching a sale popup, switching payment provider, sending an "order on its way" email and seeing in the reports what sold and where visitors came from, without calling a developer for every change.
The result in practice

What does a website for a book or a single product look like when it sells and not just displays?

When one product is the star, every page has to lead to it: a prominent buy button, a visible price and very few steps to payment. In The Great Poop Book this means quick buy from every product straight to the payment page, a side cart that does not take the customer off the page and a handwritten dedication with a preview. Extras such as a discounted children's book work best inside the cart, once the customer has already decided, and not as noise on the home page.

No less important is what happens behind the scenes: payment verified with the payment company, emails that look like the brand and reports that show what really happens on the site. That way the business owner can improve sales alone, based on data and not on feelings. You can see the result on the live site thegreatpoopbook.com. Planning a similar project? It is worth starting with website development or custom system development, checking the cost in the calculator and browsing the portfolio.

When does it make sense to move from WordPress and WooCommerce to a Laravel store?

The move is justified when the store no longer needs what WordPress offers: a small or focused catalogue, a strong brand that demands a precise experience, and business rules that are hard to build from plugins, such as a smart offer in the cart, a personal dedication or payment on a secure page with your own verification. When all this meets the burden of plugins, updates and maintenance, a clean-code store gives speed, control and less dependence. It is not always the right decision: for a simple store with a large catalogue that relies on an existing plugin ecosystem, WordPress may still fit, and we wrote the full comparison in the guide WooCommerce or a custom store.

Another example of a custom store, on a completely different scale, is the Bakes store, with over 2,600 products, a loyalty club and a digital gift card. And for the question of where to run such a store safely, we have an answer in hosting, security and maintenance.

What should you check before replacing an existing store with a new one?

The move itself is the delicate part. Product URLs have to be kept or given a 301 redirect to the matching page, the sitemap and the structured data have to be updated, and event measurement (product view, add to cart, purchase) must work from the first day. Payment is tested in test mode before moving to live mode, and the email templates for order confirmation and shipping are tested end to end. We set out the rules of the move in the guide to moving without losing rankings.

Further reading

// FAQ

Frequently asked questions

What kind of project was carried out for The Great Poop Book?
A redesign and a from-scratch build of an online store and website in Laravel, replacing a WordPress and WooCommerce site. It includes quick buy, payment on a secure hosted page (Grow or iCredit), a full admin panel, a customer account area, a popup system, internal reports and designed emails.
How does payment work on the site?
The customer goes to a secure hosted payment page of the payment company and returns to a thank-you page on the site. The site does not store card details and does not mark an order as paid before verifying the payment directly with the payment company. The site owner chooses between Grow and iCredit, and between test and live mode, from the admin panel.
How did you keep the search visibility in the move from WordPress?
The product URLs were kept exactly as on the previous site, and every old URL that changed was given a 301 redirect to the matching page. A sitemap, structured data for the product pages and commerce event measurement for Google Analytics and Meta were also built. There is no promise of ranking, but this way what already exists is not lost.
Why build a Laravel store rather than stay on WordPress with WooCommerce?
When the store is small and focused and the client wants a precise experience and control over the business rules, a clean-code store gives speed, less dependence on plugins and less maintenance. When there is a huge catalogue relying on an existing plugin ecosystem, WordPress may still fit. The decision depends on needs, not fashion.
Can a Laravel store run on shared hosting?
Yes, and that is exactly what was done for The Great Poop Book: DirectAdmin shared hosting, with no dedicated server. The code was written so that it is uploaded through the file manager and the database is installed by importing a single SQL file through phpMyAdmin, with no Composer and no terminal. For systems with a heavier load it is worth considering a dedicated server.
How does the site owner run the store without a developer?
From the admin panel: editing every heading and text on the site, including the emails, managing orders, products, coupons and pages, a popup builder with ready designs, switching the payment provider, sending an "order on its way" email and reports on views, sales and the purchase funnel. That way a promotion or a text can be changed without calling a developer.
How do you protect registration and orders from bots?
In layers: a honeypot field that only a bot would fill, a time check that detects filling too fast, a calculation challenge and Turnstile, alongside a password policy with live feedback and an attempt limit on every form. No single layer is enough, and the combination is what reduces the noise without bothering a real customer.
How much does it cost to build an online store for a book or a single product?
The price depends on the scope: the number of products, the payment provider, the account area, the admin panel and the emails. A focused store like this one is much smaller than a store with thousands of products. You can get an initial estimate in the cost calculator, and after a short discovery call we will present an exact quote.

An author, a publisher or a brand with one star product that wants a store that sells?

We build stores and websites in clean, custom code for businesses that want to start from the product and reach payment in as few steps as possible.