The plugin provides built-in integrations to core WordPress functionalities and major analytics plugins, as to help implementing a consent banner.<\/p>\n\n
Major WordPress plugins are automatically discovered and added to the banner.<\/p>\n\n
One can then fine tune the configuration or even add custom entries.<\/p>\n\n
Besides letting you manually configure purposes, the plugin provides built-in integrations to core WordPress functionalities and major analytics plugins.<\/p>\n\n
A custom editor block allows one to block any content until the user gives their explicit consent.\nThis would display a placeholder allowing the user to do so on the spot.\nWhen they does, the placeholder is replaced by the intended content.<\/p>\n\n
This block can be used around any other block or list of blocks, as the core The contextual consent placeholder can be added automatically to any Orejime is developed and updated by the Boscop teams in accordance with regulatory developments and European and French recommendations (particularly those of the EDPB and the CNIL).<\/p>\n\n However, the compliance of a cookie manager largely depends on the solution's configuration (from the handling of each cookie, to color choices, and the information provided to users).<\/p>\n\n It is your responsibility to verify your site's compliance, and Boscop cannot be held liable for any compliance issues arising from users of the Orejime plugin.<\/p>\n\n The plugin revolves around the concept of \"integrations\".\nAn integration is a bridge between Orejime and a WordPress plugin or native feature.<\/p>\n\n Every integration derives from the base For every active integration, Orejime would register an associated purpose, which allows for customizing the info that is shown to the end user.<\/p>\n\n The orejime library is provided by the plugin.\nIts source code is available at GitHub<\/a>.\nBuild files are sourced from the official npm module<\/a>, installed via npm, then copied over to the This task is run automatically by other build tasks such as This plugin helps you configure a consent banner by providing presets for commonly used plugins.\nHowever, you should always review its output and tune it accordingly.<\/p>\n\n See the legal disclaimer for more info.<\/p><\/dd>\n The full code and history is available here at GitHub<\/a>.<\/p><\/dd>\n You can use the GitHub project's issues<\/a> and discussions<\/a>.<\/p><\/dd>\n\n<\/dl>\n\n\ngroup<\/code> block.<\/p>\n\nembed<\/code> blocks.<\/p>\n\nLegal disclaimer<\/h4>\n\n
Development<\/h3>\n\n
Architecture<\/h4>\n\n
Integration<\/code><\/a> class.\nThey must each have unique identifiers and names, and should provide a way to tell if their target integration is currently active.\nThey hook into their target to alter their output, typically as to modify scripts so they can be handled by Orejime.<\/p>\n\nInitial setup<\/h4>\n\n
npm install # installs build & run environment\nnpm run up # starts docker containers\nnpm run composer install # installs backend dev environment\n<\/code><\/pre>\n\nBuild<\/h4>\n\n
npm start # builds assets and watches for changes\n<\/code><\/pre>\n\nQuality<\/h4>\n\n
npm run lint # lints JS and PHP code\nnpm run format # formats JS and PHP code\n<\/code><\/pre>\n\nOrejime integration<\/h4>\n\n
public<\/code> folder via a build task:<\/p>\n\nnpm run package-orejime\n<\/code><\/pre>\n\nnpm start<\/code> & npm run build<\/code>.<\/p>\n\n\n\n
Does using this plugin makes my website fully compliant?<\/h3><\/dt>\n
Where is the source code available?<\/h3><\/dt>\n
Where can I report issues or ask for help?<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n