FAQ

Does it change my articles? No. It only adjusts the page as it's sent to the visitor. Turn it off, and your original tables are back.

Do I need to edit my existing tables? No. Out of the box, every eligible table gets the Auto layout. Classes are only needed when you want a specific layout for a specific table.

Does it use JavaScript? No. It uses server-side HTML processing and CSS only. The "More details" toggle uses the native HTML <details> element.

Will it slow my site down? Pages without tables cost one quick text search. On pages with tables, only the tables are processed. The stylesheet is small and only loaded where it's needed. Very large pages, over the Page size limit, are skipped.

Does it work with page builders like SP Page Builder? Yes. It processes the final HTML, whatever built it, and includes fixes for common page-builder table styles. As with any template, test your key pages after installing.

Does it work in modules and other components? Yes, with Process tables in set to Whole page, which is the default. Use Article content only, the selectors, or the menu item and component rules to narrow it down.

Can I use different layouts on the same page? Yes. Give each table its own class, for example ert-cards on one and ert-scroll on another.

Does it affect the administrator area? No. It only runs on the front end.

Does it work in other languages? The admin interface is in English. You can change the visitor-facing text, the swipe hint, "More details" and the screen-reader name, to any language in the plugin settings.

Is there an editor button for choosing the layout? Not yet. It's planned for a later release. For now, use the classes and attributes above.