components-newsletter-signup

Components: Newsletter Signup

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "components-newsletter-signup" with this command: npx skills add kostja94/marketing-skills/kostja94-marketing-skills-components-newsletter-signup

Components: Newsletter Signup

Guides newsletter signup form design for list growth. Email subscribers spend 138% more than non-subscribers; top popups convert at 23%+.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-context.md exists, read it for audience and value proposition.

Identify:

  • Placement: Header, footer, popup, inline, sidebar

  • Incentive: What subscribers receive

  • Platform: Web, mobile, both

Form Design

Minimal Fields

  • Email only when possible; highest conversion

  • Add name only if needed for personalization

  • Wrong number of fields significantly impacts conversion

Value Proposition

  • Clear: what subscribers receive, how often

  • Transparent: avoid disappointing subscribers

  • Incentive: lead magnet, discount, exclusive content

Visual Design

  • Clearly clickable submit button

  • Mobile-first; responsive layout

  • Appropriate input types (e.g., type="email" for mobile keyboards)

  • Trust marks or security indicators

Placement

Placement Best For Pros Cons

Header High visibility Always visible Limited space

Footer Secondary capture Non-intrusive Lower visibility

Footer bar Persistent Sticky Can annoy

Popup High intent High conversion Intrusive

Inline Content pages Contextual Depends on scroll

  • Avoid hiding forms behind unclicked buttons/links

  • Don't place competing forms nearby

Accessibility

Requirement Practice

Labels <label> for each input; for /id association

Placeholders Don't replace labels; supplement only

Error messages Clear, associated with field

Keyboard Full tab order; submit via Enter

Touch targets ≥44×44px for submit button

Technical

  • Validation: Client-side; server-side required

  • Privacy: Link to privacy policy; GDPR/CCPA compliance

  • Double opt-in: When required by jurisdiction or best practice

Output Format

  • Form structure (fields, copy)

  • Placement recommendation

  • Value proposition suggestions

  • Accessibility checklist

Related Skills

  • channels-email-marketing: Full email marketing strategy; EDM, newsletter, deliverability, content types

  • components-footer: Footer often hosts signup forms

  • components-cta: Submit button is a CTA

  • components-trust-badges: Trust marks near form

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

google-search-console

No summary provided by upstream source.

Repository SourceNeeds Review
General

tiktok-captions

No summary provided by upstream source.

Repository SourceNeeds Review
General

branding

No summary provided by upstream source.

Repository SourceNeeds Review
General

copywriting

No summary provided by upstream source.

Repository SourceNeeds Review