OOratiq

FAQ Section

Ready

Accordion of common questions.

Installation

$ npx @oratiq-js/ui add faq-section

Copies the component and everything it depends on into your project, then lists the npm packages to install. The code is yours after this.

Usage

import
import { FaqSection } from "@/components/blocks/faq-section";

Style 02

Is it really free?

Yes — MIT. Components and blocks, commercial use included.

What about updates?

Re-run add with --overwrite and review the diff. You stay in control.

Does RTL cost extra work?

No. Flip dir on <html>; logical properties do the rest.

Can my agency use it for clients?

Yes, unlimited projects. Attribution appreciated, never required.

Which frameworks?

Next.js first-class today; the components are React + Tailwind.

Where do I report bugs?

GitHub issues — templates ask for theme and direction up front.

$ npx @oratiq-js/ui add faq-section-02

Style 03

Questions, answered

Can't find yours? We reply within a business day.

$ npx @oratiq-js/ui add faq-section-03

Style 04

Frequently asked

Still stuck?

We answer every question within a business day.

$ npx @oratiq-js/ui add faq-section-04

Style 05

Licensing

Technical

$ npx @oratiq-js/ui add faq-section-05

Style 06

14 days, no questions asked.

$ npx @oratiq-js/ui add faq-section-06

What a block is

  • A full section, composed from the components in the sidebar — copy it in, replace the demo content, ship.
  • Every style is its own registry item: the command under each preview installs exactly that file.
  • Blocks read the same semantic tokens as everything else — your brand override applies instantly.
  • Logical properties throughout: flip dir on <html> and any style mirrors.

Content is yours

The text, links, and data inside are demo content by design. Blocks are starting points, not configurable widgets — edit the file directly.

View source on GitHub → components/blocks/faq-section.tsx