=== Ethan's Expandable Accordion Designer ===
Author: Ethan J. Hulbert
Author URI: https://www.ethanjhulbert.org/?r=eeadapp
Plugin URI: https://www.ethanjhulbert.org/free-wordpress-themes-plugins/expandable-accordion-designer-wp-plugin/?r=eeadapp
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

== Description ==

Build accessible, shortcode-driven accordions. Define as many independent
"types" as you like from the settings screen (Accordion Designer, in the
admin menu) -- each with its own default open/closed state, heading level,
icon, animation, colors, and a raw Custom CSS field -- then drop the
[eead_accordion] shortcode anywhere content is allowed.

== Shortcode usage ==

    [eead_accordion type="simple-faq"][trigger]Is this thing accessible?[/trigger]
    Yes -- the trigger is a real button, the panel is a labeled region, and
    closed content is still present in the page's HTML source at all times.
    [/eead_accordion]

Attributes:

* type    (required) -- the slug of a type defined on the settings screen.
* open    (optional) -- "true" or "false". Overrides the type's default
  open/closed state for this one instance.
* heading (optional) -- one of h1-h6 or div. Overrides the type's default
  heading level for this one instance. Affects semantics only, never
  visual styling.
* id      (optional) -- a custom id for this instance, usable for
  deep-linking (see below). If omitted, one is generated automatically.

Each accordion is its own shortcode instance; use multiple
[eead_accordion] shortcodes for multiple accordions. All accordions are
independent -- opening one never affects any other.

== Deep linking ==

Link to `#your-id` (the accordion's id, or the auto-generated one you can
see by inspecting the rendered page) to have that accordion open and
scroll into view automatically when the page loads, if JavaScript is
available. This is a progressive enhancement: without JavaScript, the
linked page loads normally at the type's configured default state.

== Custom CSS per type ==

Every type's wrapper carries a stable `.eead-type-{slug}` class. Use this
as the scoping selector in that type's Custom CSS field so your rules
apply only to that type, e.g.:

    .eead-type-simple-faq .eead-trigger { font-weight: 600; }

== Notes ==

Requires the block/classic editor's shortcode support (standard in
WordPress). No build step; no external dependencies beyond WordPress
core (media library, color picker, and code editor components, all
already bundled with WordPress).
