Blabber Footer Banner#22
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new banner location, "Blabber Footer Start," specifically for the Blabber theme. It allows banners to be displayed just above the footer area with support for multiple banners, device targeting, and responsive design. The update also includes styling, documentation, and code changes to integrate this feature seamlessly into the plugin.
Feature Addition: Blabber Footer Start Banner Location
blabber_footer_start, to display banners just above the footer in the Blabber theme. This includes JavaScript-based insertion and support for multiple banners with device targeting. (1, 2)Documentation Updates
README.mdto include details about the new "Blabber Footer Start" banner location, its purpose, and usage guidelines. (1, 2)Versioning and Changelog
1.8.0and updated theCHANGELOG.mdto reflect the addition of the new feature and related changes. (1, 2, 3)