Premium About Page Direction

Present EpubReaderly as a welcoming place to explore an EPUB reader, understand EPUB files, and find practical digital-reading guidance. The visual language should feel like a premium digital publication: spacious, minimal, book-inspired, and modern.

• Use editorial typography, chapter-number motifs, document outlines, page edges, open-book illustrations, and restrained teal accents.
• Avoid stock photography, product screenshots, dashboards, fictional people, testimonials, statistics, awards, and invented company history.
• Use the official palette: #F5F5F5, #48CFCB, #229799, #424242, plus white surfaces.

1. Premium editorial hero: “Making Digital Reading Easier to Explore.”
2. What Is EpubReaderly?
3. Our Purpose: helping readers understand and explore EPUB files.
4. Why EPUB Matters: accurate, educational EPUB information.
5. What You’ll Find on EpubReaderly: reader, features, blog, and FAQs.
6. Who EpubReaderly Is For: readers, students, authors, researchers, and publishing learners.
7. Our Approach to Digital Reading: a manifesto-style principles section.
8. Getting Started: a three-step reader and resources journey.
9. Six accessible About FAQs.
10. Final dark CTA inviting visitors to open the EPUB reader or contact support.

Use natural, publish-ready copy focused on the primary keyword “epub reader” without keyword stuffing. Keep claims factual: describe EPUB generally, and do not imply that every EPUB capability is an EpubReaderly feature.

• EPUB reader: /
• Features: /features
• Blog: /blog
• FAQs: /faqs
• Contact: /contact
• Support email: support@epubreaderly.com

Give every section a distinct composition: two-column hero, asymmetric explanatory layout, horizontal principles, educational split layout, resource grid, audience mosaic, numbered manifesto, connected timeline, accordion, and dark CTA.

• Maximum inner width: 1350px.
• Desktop: editorial split layouts and a horizontal three-step timeline.
• Tablet: preserve hierarchy with adaptive columns.
• Mobile: stack split layouts, use a vertical timeline, maintain touch targets, and prevent horizontal overflow.
• Use Boxicons only when implementation is requested.

When implementation is requested, provide one self-contained WordPress + Divi + WP Coder snippet with HTML, scoped CSS, and vanilla JavaScript only.

• Scope all styles and scripts to #epubreaderly-about using uniquely prefixed classes.
• Do not recreate the site header or footer, include PHP, or use global CSS selectors.
• Use semantic HTML, one H1, logical heading order, descriptive links, visible focus states, sufficient contrast, and reduced-motion support.
• The FAQ accordion must use semantic buttons with correct aria-expanded and aria-controls, keyboard support, lightweight transitions, and duplicate-initialization protection.