Super Footer for GrapesJS
What's Included
- Source code package (project files)
- Production-ready dist build
- Commercial license
- Future updates included
GrapesJS Compatible
Tested with GrapesJS 0.21.x, 0.20.x, 0.19.x, 0.18.x, 0.17.x, 0.22.x
Source Code Included
Full source + production-ready dist build
Editor Compatible
Designed for the GrapesJS open-source editor
Commercial License
Use in client projects without restrictions
Build once. Apply everywhere. Manage your site’s footer with zero hassle.
The Super Footer Plugin brings effortless footer management to GrapesJS. Instead of recreating or updating footers page by page, this plugin lets you design a single global footer (or multiple variations) and apply them consistently across your entire project. Perfect for teams, freelancers, and agencies who value speed, consistency, and brand alignment.
Working only with Pages Manger by GrapesJS. In demo uses this Pages Manager plugin.
Why You’ll Love It
-
🚀 One-click global footers
Create once, update once — changes instantly reflect on every page. -
🗂 Multiple footers & categories
Organize different footers for different site sections, clients, or projects. -
🎨 Fully customizable
Works seamlessly inside GrapesJS — edit with the same tools you already use. -
⚡ Fast & intuitive UI
Designed with productivity in mind. No extra setup, no steep learning curve. -
💼 Professional results
Keep your projects consistent, polished, and client-ready.
Perfect For
-
Agencies managing multi-page websites
-
Freelancers who need reusable, client-specific footers
-
Anyone tired of updating the same footer manually on every page
Ratings:
No reviews yet. Be the first to share your experience.
Questions & Answers
No questions yet. Have something to ask?
Common problems this plugin can help fix
Real community questions on the same topic — see how others worked around them.
- #3975💬 2 answers
Background Image Starts duplicating in all the pages if we add only for one page
- #5570💬 3 answers
Import button is removing all styling from all pages.
- #5379✓ Solved · 4
Class modifications of components are not automatically detected
- #5199💬 3 answers
Changes in component's attributes being reproduced in all the instances instead of just one
