PHPackages gridelementsteam/gridelements - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. gridelementsteam/gridelements ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility) gridelementsteam/gridelements ============================= Be part of the future of TYPO3! Support Gridelements now and unlock exclusive early access to Version 13! The well-established Gridelements Version 12 elevates TYPO3 by bringing grid-based layouts to content elements, with powerful features like advanced drag & drop and real references. Supercharge your backend workflow and make daily tasks easier. Join us in creating the next exciting version: https://coders.care/for/crowdfunding/gridelements 12.0.0(1y ago)62.3M—5%31[8 issues](https://github.com/CodersCare/gridelements/issues)[11 PRs](https://github.com/CodersCare/gridelements/pulls)20GPL-2.0-or-laterPHPPHP ~8.1.0 || ~8.2.0 || ~8.3.0 Since Dec 16Pushed 1y ago7 watchersCompare [ Source](https://github.com/CodersCare/gridelements)[ Packagist](https://packagist.org/packages/gridelementsteam/gridelements)[ Docs](https://extensions.typo3.org/extension/gridelements)[ RSS](/packages/gridelementsteam-gridelements/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependencies (18)Versions (56)Used By (20) [![Latest Stable Version](https://camo.githubusercontent.com/304ffa536bc8712091ba0f7b313f29bc2a3d7ab1d66a80c24b778799e86675e1/68747470733a2f2f706f7365722e707567782e6f72672f67726964656c656d656e74737465616d2f67726964656c656d656e74732f762f737461626c65)](https://extensions.typo3.org/extension/gridelements/)[![TYPO3 11](https://camo.githubusercontent.com/95b97bf30b8b5b6165cafd25cef0d9dac36c06ceae2a71021f6c58bd39e30843/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f5459504f332d31312d6f72616e67652e7376673f7374796c653d666c61742d737175617265)](https://get.typo3.org/version/11)[![TYPO3 10](https://camo.githubusercontent.com/cc1b7063888c8b51454eba1d97cf837c15676c490188a6f0e9400137eebac772/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f5459504f332d31302d6f72616e67652e7376673f7374796c653d666c61742d737175617265)](https://get.typo3.org/version/10)[![Total Downloads](https://camo.githubusercontent.com/c3d99216f1b4787d7f55bc124d98a822e7eca9b3cb5137848bb21aa97f5ceb47/68747470733a2f2f706f7365722e707567782e6f72672f67726964656c656d656e74737465616d2f67726964656c656d656e74732f642f746f74616c)](https://packagist.org/packages/gridelementsteam/gridelements)[![Monthly Downloads](https://camo.githubusercontent.com/ccf4d9658beb65dab1f53eeff9f04f5fc66808a0b59f23519aff18cb7c64d1e7/68747470733a2f2f706f7365722e707567782e6f72672f67726964656c656d656e74737465616d2f67726964656c656d656e74732f642f6d6f6e74686c79)](https://packagist.org/packages/gridelementsteam/gridelements) TYPO3 extension `gridelements` ============================== [](#typo3-extension-gridelements) This TYPO3 extension extends the grid-based concept known from the backend layout of pages to regular content elements - the grid elements. The grid elements are - just like backend layouts - defined by TypoScript and can thus be easily reused, extended and put under version control. It allows nesting of grids, giving the backend editor a wide range of layout possibilities. Its container nature encourages grouping content elements and assigning them specific frontend renderings, for example to display an accordion, tabs or galleries. Grid elements can be referenced to keep the content structure slim. The focus is always on the usability of the backend editor, which is supported by an advanced drag & drop handling and a granular configuration setting to define rules per grid element. This approach is an alternative to the *TemplaVoilà!* template engine, which uses XML in database fields to store relations and provides less convenience across all components. URL**Repository:****Read online:****TER:**Inspiring people to share ------------------------- [](#inspiring-people-to-share) We strongly believe in the principles of Open-source software, which is why we share this TYPO3 extension with you completely free of charge. Still even contributors to Open-source projects have to make a living somehow, so even though you are not obliged to do so, you should consider sharing a small part of the money you might be earning with this extension in return. This way we can make sure to still provide the TYPO3 community with better extensions and services in the future. Thanks in advance for your support. How to support our efforts? --------------------------- [](#how-to-support-our-efforts) [![CodersCareLogo](Documentation/Images/Sponsoring/CodersCareLogo.png)](https://coders.care/for/crowdfunding/gridelements)Support the development of Gridelements and other extensions by becoming a sponsor! As a sponsor, you'll gain exclusive early access to the latest features and updates, making your workflow even more efficient.[![PatreonLogo](Documentation/Images/Sponsoring/PatreonLogo.png)](https://www.patreon.com/cybercraft)A Service which allows you to become one of our Patrons on a monthly basis. You might even get a shout-out on twitter, get mentioned personally in the next release or even make a feature request depending on the amount you pick.[![FlattrLogo](Documentation/Images/Sponsoring/FlattrLogo.png)](https://www.flattr.com/@Cybercraft)Pay any amount monthly on this service and it gets spread even around the people you want to support! We would be Flattr'ed to have you.[![PaypalLogo](Documentation/Images/Sponsoring/PaypalLogo.png)](https://www.paypal.me/cybercraftsponsoring/50)You don't want to sponsor monthly? Don't worry you can also support us via Paypal with any desired amount you find reasonable.[![AmazonWishlistLogo](Documentation/Images/Sponsoring/AmazonLogo.png)](https://www.amazon.de/gp/registry/wishlist/2I80GX9ZSMYXX)Sometimes you want to give it a personal touch. When you want to thank Joey and Petra with a nice Single Malt, you should take a look here. Slàinte mhath!The Agreement ------------- [](#the-agreement) Excerpt from the coders.care blog post [Service Level Agreements for TYPO3 Extensions](https://coders.care/blog/article/service-level-agreements-for-typo3-extensions) [![Big Orange rope pulling several colorful small ropes](Documentation/Images/Sponsoring/Why.jpg)](Documentation/Images/Sponsoring/Why.jpg) ### Enabling companies, developers and the community to join forces and thrive [](#enabling-companies-developers-and-the-community-to-join-forces-and-thrive) There is one particular thing, that should be different to most of the variants of service level agreements provided by other open-source projects though. Having to buy a so called "enterprise" or "professional" edition of the extensions or TYPO3 itself just to become entitled for an SLA is a No-Go, since it will create two classes in the community and contradict the principles of free software implied by the GPL. The benefit for the people agreeing to a certain service level should be defined by reliability and responsiveness, not by getting access to something, that is unavailable for the rest of the community. So there must be an agreement to still share the improved public extensions with everybody in the community while getting a personal early or immediate access depending on the level and the priority you paid for. For developers there is the need for another agreement: They have to accept and publish fixes and changes to their extensions up to a certain degree, so the whole pool of developers can take care of the extensions covered by the SLAs. This will avoid forks. There are several nice side effects of these agreements. For example it would reduce the number of extensions which are maintained by a single person and therefore the risk of loss when using these extensions. Due to the four-eyes principle this would increase the quality of each extension in the approved pool and at the same time reduce the amount of "me too" extensions in the TER. There would be a powerful team of developers backing the service levels, so it would be easy to keep the approved extensions on a level with upcoming versions of the TYPO3 core. And since this would be done in close collaboration with the TYPO3 core team and the security team, core bugs and security holes affecting extension behaviour could be fixed and published much more easily as well. ### Health Score 54 — FairBetter than 97% of packages Maintenance24 Infrequent updates — may be unmaintained Popularity49 Moderate usage in the ecosystem Community41 Growing community involvement Maturity92 Battle-tested with a long release history Bus Factor1 Top contributor holds 89.4% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~66 days Recently: every ~233 days Total 50 Last Release 550d ago Major Versions 8.8.0 → 9.8.02022-04-25 9.8.0 → 10.3.02022-04-25 8.8.2 → 10.4.22022-04-26 10.4.3 → 11.0.02023-04-28 11.1.0 → 12.0.02024-11-14 PHP version history (2 changes)11.1.0PHP ^7.4 || ^8.0 || ^8.1 || ^8.2 12.0.0PHP ~8.1.0 || ~8.2.0 || ~8.3.0 ### Community Maintainers ![](https://www.gravatar.com/avatar/8d470f4d638f73446668ac0eec1b596798a6cbe62027667cd950e6bb9b4ec047?d=identicon)[Bunnyfield](/maintainers/Bunnyfield) ![](https://www.gravatar.com/avatar/11d37a7939567977c6b3fa9f480b6f7843428e041e8d76a9c539301f1be65eae?d=identicon)[Coders.Care](/maintainers/Coders.Care) --- Top Contributors [![Bunnyfield](https://avatars.githubusercontent.com/u/3198454?v=4)](https://github.com/Bunnyfield "Bunnyfield (924 commits)")[![liayn](https://avatars.githubusercontent.com/u/222377?v=4)](https://github.com/liayn "liayn (27 commits)")[![lochmueller](https://avatars.githubusercontent.com/u/3907126?v=4)](https://github.com/lochmueller "lochmueller (15 commits)")[![mkroener](https://avatars.githubusercontent.com/u/112870221?v=4)](https://github.com/mkroener "mkroener (9 commits)")[![Fischtbengel](https://avatars.githubusercontent.com/u/109543974?v=4)](https://github.com/Fischtbengel "Fischtbengel (7 commits)")[![Coders-Care](https://avatars.githubusercontent.com/u/28861531?v=4)](https://github.com/Coders-Care "Coders-Care (5 commits)")[![helhum](https://avatars.githubusercontent.com/u/904370?v=4)](https://github.com/helhum "helhum (5 commits)")[![aertmann](https://avatars.githubusercontent.com/u/903567?v=4)](https://github.com/aertmann "aertmann (4 commits)")[![nhovratov](https://avatars.githubusercontent.com/u/19343425?v=4)](https://github.com/nhovratov "nhovratov (3 commits)")[![ErHaWeb](https://avatars.githubusercontent.com/u/5416710?v=4)](https://github.com/ErHaWeb "ErHaWeb (3 commits)")[![kc-GitHub](https://avatars.githubusercontent.com/u/1027385?v=4)](https://github.com/kc-GitHub "kc-GitHub (3 commits)")[![3l73](https://avatars.githubusercontent.com/u/4559579?v=4)](https://github.com/3l73 "3l73 (3 commits)")[![sypets](https://avatars.githubusercontent.com/u/13206455?v=4)](https://github.com/sypets "sypets (3 commits)")[![wtfred](https://avatars.githubusercontent.com/u/3072924?v=4)](https://github.com/wtfred "wtfred (2 commits)")[![pniederlag](https://avatars.githubusercontent.com/u/85458?v=4)](https://github.com/pniederlag "pniederlag (2 commits)")[![sir-gawain](https://avatars.githubusercontent.com/u/615812?v=4)](https://github.com/sir-gawain "sir-gawain (2 commits)")[![smichaelsen](https://avatars.githubusercontent.com/u/912435?v=4)](https://github.com/smichaelsen "smichaelsen (2 commits)")[![tlayh](https://avatars.githubusercontent.com/u/285669?v=4)](https://github.com/tlayh "tlayh (2 commits)")[![rafu1987](https://avatars.githubusercontent.com/u/2694825?v=4)](https://github.com/rafu1987 "rafu1987 (1 commits)")[![rl-saen](https://avatars.githubusercontent.com/u/57944193?v=4)](https://github.com/rl-saen "rl-saen (1 commits)") --- Tags TYPO3 CMSgridsGridelements ### Code Quality Static AnalysisPHPStan Type Coverage Yes ### Embed Badge ![Health badge](/badges/gridelementsteam-gridelements/health.svg) ``` [![Health](https://phpackages.com/badges/gridelementsteam-gridelements/health.svg)](https://phpackages.com/packages/gridelementsteam-gridelements) ``` ### Alternatives [fluidtypo3/flux The flux package from FluidTYPO3 152982.2k20](/packages/fluidtypo3-flux)[fluidtypo3/vhs This is a collection of ViewHelpers for performing rendering tasks that are not natively provided by TYPO3's Fluid templating engine. 1954.1M49](/packages/fluidtypo3-vhs)[friendsoftypo3/content-blocks TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML 96374.6k23](/packages/friendsoftypo3-content-blocks)[brotkrueml/schema Embedding schema.org vocabulary - API and view helpers for schema.org markup 33584.6k13](/packages/brotkrueml-schema)[yoast-seo-for-typo3/yoast_seo Yoast SEO for TYPO3 521.6M9](/packages/yoast-seo-for-typo3-yoast-seo)[eliashaeussler/typo3-form-consent Extension for TYPO3 CMS that adds double opt-in functionality to EXT:form 1481.0k](/packages/eliashaeussler-typo3-form-consent) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)