Lightweight Accordion vs Make Me Static, Static Site Generator, Git, Pages and Live Stats

Lightweight Accordion plugin for WordPress allows you to add collapse elements to posts using a Gutenberg block or a shortcode (via classic editor). By using the details HTML tag and a few lines of CSS this allows for a javascript-free accordion for minimum page load. Extremely Lightweight (<1kb): Without using Javascript the plugin uses the native details HTML tag and a few lines of code for almost no impact on front-end. Customizable: Options include customizing the HTML tag used for the accordion title, open by default, borders, colors, and accordion grouping (auto-close others when one opens). Shortcode Usage examples Here are a few examples of using the accordion plugin with shortcodes. [lightweight-accordion title="My Accordion"]My Content[/lightweight-accordion] Additionally you can display the accordion open on load with the accordion_open option. [lightweight-accordion title="My Accordion" accordion_open=true]My Content[/lightweight-accordion] You can also change the html tag wrapping the title of the accordion using the title_tag option. [lightweight-accordion title="My Accordion" title_tag="h3"]My Content[/lightweight-accordion] If you want to include FAQ schema you can add the schema option and set it to faq. [lightweight-accordion title="What is your return policy?" schema="faq"]You have 1 week to return your items[/lightweight-accordion] If you’d like put a border around the content of the accordion you can use the “bordered” attribute. [lightweight-accordion title="Bordered Content" bordered=true]My Content[/lightweight-accordion] If you want accordions to auto-close when another opens (exclusive accordion), use the “group” attribute with the same value on each accordion. [lightweight-accordion title="Question 1" group="faq"]Answer 1[/lightweight-accordion] [lightweight-accordion title="Question 2" group="faq"]Answer 2[/lightweight-accordion] [lightweight-accordion title="Question 3" group="faq"]Answer 3[/lightweight-accordion] If you’d like to swap the default triangle marker for a chevron or plus/minus icon (optionally on the right side of the title) use the “icon” and “icon_position” attributes. [lightweight-accordion title="My Accordion" icon="chevron" icon_position="right"]My Content[/lightweight-accordion] Shortcode Options Here is the full listing of shortcode options. Additionally all of these options are accessible when using the Gutenberg block. title (Required Default: null) The title of your accordion will be displayed at the top for users to click. A good example would be to include a user’s question so they could click it for more details. content (Required Default: null) Content that will go into your accordion element. title_tag (Default: “span”) This sets the html tag that wraps the title in the accordion summary. Useful if you want to make it a heading tag for SEO purposes. accordion_open (Default: false) Set this to true if you want your accordion to be open by default. bordered (Default: false) Set this to true if you want a border around the accordion content. title_text_color (Default: false) Set this to a hex value or CSS color to change the color of the accordion title text. title_background_color (Default: false) Set this to a hex value or CSS color to change the color of the accordion title text. schema (Default: false) Set this to faq if you’d like FAQ schema to be included. class (Default: false) Used to add a custom class to the parent container of the accordion. anchor (Default: null) Adds the value as an ID to the accordion div as an anchor. autop (Default: true) By default the shortcode will wrap text in a ‘p’ tag. Set this to false if you’d like this disabled for the specific accordion. group (Default: false) Set this to a group name to make accordions with the same group auto-close when another opens. Uses the native HTML details name attribute for zero JavaScript overhead. icon (Default: false) Set this to “chevron”, “plus”, or “none” to replace the default triangle marker. The chevron rotates and the plus becomes a minus when the accordion opens. icon_position (Default: false) Set this to “right” to display the chevron or plus icon on the right side of the accordion title. Additional Details If you’d like to remove the “lightweight-accordion.css” from being enqueued on your site use the filter below. It’s recommend you style the accordion yourself if you use this filter. add_filter('lightweight_accordion_include_frontend_stylesheet', '__return_false' ); If you’d like to remove the “lightweight-accordion/editor-styles.css” from being enqueued in the admin area of your site you can use the filter below. add_filter('lightweight_accordion_include_admin_stylesheet', '__return_false' ); If you’d like to remove processing of shortcodes in accordion content you can use this filter. add_filter('lightweight_accordion_process_shortcodes', '__return_false' ); If you’d like to use inline Microdata for FAQ schema you can use this filter. (Not recommended) add_filter('lightweight_accordion_output_microdata', '__return_true' ); If you’d like to force “lightweight-accordion.css” to load on all of your site you can use this filter. By default the plugin will detect if the block or shortcode is used and enqueue the CSS. add_filter('lightweight_accordion_always_include_frontend_stylesheet', '__return_true' ); When a page contains an accordion a tiny inline script is added to the footer that automatically opens accordions targeted by a URL hash (for example a link to an accordion’s anchor). If you’d like to disable this you can use the filter below. add_filter('lightweight_accordion_anchor_script', '__return_false' );

Welcome to the Make Me Static Plugin for WordPress. This plugin is a static site generator and aims to create and maintain a static copy of your WordPress website within a Git repository. This version includes automatic access to a free Git solution and Page provider platform. (so no setup or credentials are necessary) Alternatively the static site can be generated and stored in a GitLab Git Repository that can be used as a source for a static page platform such as CloudFlare Pages. The plugin provides customised sitemap and change tracking which connects to an external crawling service which does all the heavy lifting. We have made great efforts in this version to minimise the configuration required to get going, if you have any problems (with anything) please let is know and we’ll do our best to help. Check out this YouTube video for an introduction to static front-ends and a walk-through of converting a pre-existing WordPress site into a WordPress site with a static front-end. How the service works The plugin connects to a directory service on the Internet at one of the directory URL’s listed below. This in turn will point the plugin to a ‘crawler’ that has been allocated to your site. When you ask the plugin to make a static copy of your site, it will instruct the crawler to visit all the pages on your site to determine which have changed since it’s last visit. Any changed pages will be copied to a Git repository, which in turn can publish pages directly to a page hosting service. The default option is to use a Git account hosted by MadPenguin, and to publish the site on MadPenguin’s page hosting platform. As a result the default options do not require any specific Git or Page hosting configuration to get going. If on the other hand you choose to use a hosted Git service such as GitLab, you will need to enter some credentials for your online account, and from there configure your GitLab account to publish to a page hosting service. Once you have successfully published a static copy of your site, all you need to do is point your domain at the address of the page hosting service, and asssuming your domain matches the one you entered when setting up your profile within the plugin, you should be up and running. The service retains a metadata database for the site which includes file names, sizes and modification times, together with any credentials that have been added when creating a profile. (Sensitive credentials and other information is encrypted at rest). The external service is responsible for all scanning and processing activities to mitigate strain on the WordPress server. The only private data transferred to the external service is the information you enter when creating a profile. All other information is obtained via an anonymous external scan, hence publically available. If you have selected the default Git option, then the service will also retain a static copy of the site. Useful references The service product page Terms and Conditions of Service Privacy Policy Getting Started Service Status Support Forum Make me static directory service URL’s; https://mms-directory-1.madpenguin.uk https://mms-directory-2.madpenguin.uk https://mms-directory-3.madpenguin.uk Other URL’s used to load code; https://assets.makemestatic.com, source for stage-2 crawler UI https://status.makemestatic.com, endpoints that indicate the currently deployed version of a site https://weblogs.makemestatic.com, source for dynamically loaded weblogs data / websockets https://mms-crawler-*.madpenguin.uk, location of the actual crawlers (via websocket) Note that this in an integrated solution, the 3rd party crawling service is owned and operated by the plugin authors on a combination of cloud hosted and on premesis equipment. Live Web Statistics (experimental) If you opt to use the integrated Pages platform, this also provides a live WebStats option that uses the following URL; https://weblogs.makemestatic.com This allows live webstats to be seamlessly delivered into your control panel and updated in real-time via a websocket connection. Do not use this URL directly! This URL is only referenced once you click on the webstats icon next to your profile. How Does it work? The WordPress site is scanned by the MMS service under direction from the WordPress plugin. This off-loads the scanning process to specialised software which aims to minimise the loading on the WordPress server while scans are in progress. There are three types of scan that can be performed; An “update”, which literally only looks at entries with changed sitemap timestamps (this is very quick and great for typo’s and any changes that only affect a single page) A “synchronise”, typically this will scan every asset on the WordPress site and compare a checksum of each asset against it’s database to see if it’s changed since the last scan. Any changes are then transferred to the connected Git repository. A “Git verification”, this is like a “synchronise”, but also scans the Git repository for assets that are no longer referenced by the site (and removes them). As the site is scanned “from the outside” there should be no risk of the plugins actions exposing any data that isn’t already public. By the same token the external service has no ability to modify WordPress so the security footprint of the plugin is tiny. Feature bullet points The plugin provides a way to produce a static copy of your website in a git repository The result is compatible with both Github pages and CloudFlare pages for automatic publication Multiple profiles are supported for (A+B_…) testing Various scan rates are supported from one page per 5s to 7 cores flat out Scheduled updates are supported and automated scanning Currently “Gitlab” is supported with plans for GitHub and on-prem Gitlab Support push services (WebPushr) to automatically notify subscribers on scan completion Issue tracker for each profile to diagnose problems Handles current and historical issues Ability to acknowlede or delete issues when resolved GUI access to the internal asset database Search as you type filtering Pinning (force assets to be scanned regardless of perceived change) Selective / manual queueing of assets for testing Ability to include manual / static assets in the scan (in the WP tree but unmanaged by WP) Ability to exclude specific files and folders Setup Wizard is included for a guided profile creation The Technology The Plugin presents as a WordPress Admin / plugin page Backend connections are made over websockets using PKI The crawler respects Robots.txt, (make sure the “MMSbot” agent is allowed on your site) MMS Javascript runs in an isolated module and CSS “plays nice” with WordPress Global CSS and theming is partitioned and user editable (if you feel the need …) All of the front-end JS code and PHP is either GPL2 or MIT licensed Backend-code is all based on the Orbit Framework (the framework and DB are all MIT licensed) Orbit is a ‘real time’ framework, so the admin panel is 100% reactive. Progress bar updates are typically “per percent” granularity All statuses, totals, etc, are updated as they happen Unless you’ve hit a bug, there is no mileage in reloading the MMS plugin page If you change your license information, it will change in real-time If the crawler allocated to your site changes (perhaps due to a license upgrade) then the appropriate version of the crawler UI will be uploaded “into” the page from the new crawler.