Codeinwp / Codeinwp/otter-blocks

Expand landing page block pattern library and enhance page builder theme integration

Open
#3,038 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request-triage
Dominant language
JavaScript
Stars
198
Forks
36
Avg merge
3d 4h
Merged PRs (30d)
30

Description

Impact: 65 · Confidence: 90 · Complexity: 45

Description

  1. Problem: Users building landing pages in WordPress need more turnkey block pattern designs tailored for high-converting landing page structures (e.g. lead capture heroes, feature showcases, call-to-action sections) and seamless visual integration across popular page builder/block themes.

  2. Desired Behavior: Provide an expanded collection of pre-built landing page block patterns within the Otter Design Library, along with improved styling/layout compatibility when used alongside popular WordPress page builder themes.

  3. Acceptance Criteria:

  • Add a dedicated set of landing page patterns (heroes, lead capture, sales sections, CTAs) to the Otter Design Library.
  • Ensure patterns adapt cleanly to font and layout defaults of major page builder themes without CSS/spacing breakages.
  • Verify patterns render properly across mobile, tablet, and desktop viewports.

Customer Context

Submitted independently across 2 in-app feedback submissions for Otter Blocks v2.2.5. Users expressed a need for more landing-page-focused pre-built block patterns and better integration with popular page builder themes.

Root Cause Analysis

Users designing landing pages often struggle to assemble full landing page layouts from individual blocks or generic section patterns. They need pre-composed, conversion-oriented landing page patterns that seamlessly inherit and respect visual styles across various WordPress page builder themes.

Reasoning

Both feedback entries in this batch submit identical requests asking for expanded pre-built block patterns tailored for landing pages as well as improved compatibility/integration with popular page-builder themes. Since both entries submitted the exact same ask, they are consolidated into a single distinct feature request entry.


Source: automated in-product feedback — otter-blocks, 2026-09-07
Generated by feature-request-triage workflow (ID: feature-request-triage_6a9f9b0956b053.86275032)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the Otter Design Library and its existing block patterns, then review how they inherit styles from popular page builder themes. Add the requested landing-page pattern set and verify that typography, spacing, and layouts remain intact across mobile, tablet, and desktop viewports.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript, wordpress
Domain
design, frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.