Scrollchart

No. The plugin works out of the box. Scrollchart.com is a free public library.

Yes. The plugin registers native elements for WPBakery Page Builder and Elementor. Both work alongside the standard block editor and shortcode.

No. Diagrams below the fold defer loading until they scroll into view, and the JavaScript runs only on pages that actually have a diagram. The plugin caches diagram metadata locally so repeat page-loads don't hit the network.

Yes. The block, WPBakery element, and Elementor widget all expose theme, accent colour, custom hex colours, border, and background controls. Set defaults in Settings -> Scrollchart so every embed inherits them automatically.

Yes. Each embedded diagram outputs a small schema.org ImageObject block (JSON-LD) describing that diagram — its title, description and preview image — so search engines can understand and potentially surface it in image and rich results. The markup only ever describes the real diagram on the page; nothing is fabricated. If you prefer not to output it, a developer can disable it with add_filter('scrollchart_enable_jsonld', '__return_false').

Yes. Diagrams are responsive (no horizontal scrolling on mobile), respond to system dark-mode preference when theme is set to Auto, and don't rely on any AMP-incompatible techniques.

Visit scrollchart.com, find a diagram you like, and click the embed button. The slug is the kebab-case identifier in the snippet — for example, the slug for the RIR / RPE Scale diagram is rir-rpe-scale.

Yes. Visit scrollchart.com/request-a-diagram. Most custom requests are turned around within 72 hours.

Yes. All of the plugin's JavaScript and CSS ships inside the plugin itself — nothing executable is loaded from a remote server. But to display the live, interactive diagrams, the bundled loader connects to scrollchart.com at runtime for diagram DATA:

• It fetches each diagram's metadata from scrollchart.com/api/diagram (cached locally on your server so repeat page-views do not hit the network). Only the diagram slug you embedded is sent.
• It loads the interactive diagram view in an iframe from scrollchart.com/embed-frame/.
• It sends a view ping to scrollchart.com/api/ping. The ping sends the diagram slug and the URL of the page the diagram is embedded on. We use this to show authors where their diagrams are being used and to periodically check that the embed is still live on that page. No cookies are set and no visitor-identifying data (no IP stored long-term, no user agent, no fingerprint) is collected. Note that a page URL can itself contain information placed there by the site (for example a username or token in the path or query string); if that is a concern for a particular page, do not embed a Scrollchart diagram on it.
• Periodically (at most once every 15 minutes per diagram) it asks scrollchart.com/api/diagram-rev whether a diagram's content has changed, so your cached copy stays fresh. Only the diagram slug and your site host are sent. This is a lightweight read; no visitor data is involved.
• Footer placement. Enabled by default, and can be switched off at any time in Settings → Scrollchart → Advanced ("Footer placement"). When enabled, ScrollChart may place a small, on-brand line with one link at the bottom of your home page only. We design it to fit your site — written to reflect and enhance your own brand and message, styled to match, and kept subtle. The exact wording, styling and link are configured together with you. Technically, a small loader on the home page requests that configuration from scrollchart.com/api/site-footer, sending only your site host; when the option is off, the loader is not added to the page and no request is made.

• The catalogue browser loads the list of available diagrams from scrollchart.com/api/catalog.json. This is a read-only request; no data about you, your site, or your content is sent. The result is cached on your server for an hour.
• When a logged-in editor uses the optional Generate with AI button, the editor's typed prompt, and an email address only if the editor chooses to enter one, are sent from your server to scrollchart.com/api/generate.php, which returns a generated diagram. This happens only when an editor actively clicks Generate; it never runs for site visitors and never runs on the front end. If you do not use the AI generator, no prompt data is ever sent.
• When you design or save your own diagram in the editor, the diagram's content (the chart type, labels, values and styling you set) is sent to scrollchart.com/api/user-diagram so it can be stored and given a reusable ID you can re-open and edit later. Listing and deleting your saved diagrams use the same endpoint. This runs only when you actively design, save, or manage a diagram in the editor.
• To link your saved diagrams to your site (so only your site can edit them), the plugin registers your site once with scrollchart.com/api/site-register, sending only your site's home URL and receiving a per-site key it stores locally. This happens on activation, on plugin update, and the first time the editor loads if a key is not yet present. When the plugin is deleted, it sends a one-time notice to scrollchart.com/api/site-deactivate (again, only your home URL) so the service knows the install was removed; this does not delete any diagrams you created.

All JavaScript ships human-readable except the front-end loader assets/embed.js, which is minified for size. Its full commented source is included in the plugin at assets/source/embed.src.js, and is also published at scrollchart.com/embed-loader-source.txt. Build instructions (a single esbuild minify step, no bundling) are in BUILD.md in the plugin source. Every other script (the editor bundle, the WPBakery and Elementor editor glue, the block editor script) is shipped unminified.