![umbraco data type grid umbraco data type grid](https://i.stack.imgur.com/C0N8F.jpg)
Somewhere in the middle of summer (August 2019?), the Doc Type Grid Editor package was handed over to Søren Kottal who initially began the conversion of the existing version into a v8 supported one.Ī lot of Umbraco developers cheered as DTGE was extremely popular amongst all builds and allowed us to define grid editors (single units within grid cells, columns and rows), using the same, well-known approach of using document types for it. All of it must be defined and created inside of the document type definition and then processed in the code. Full control over the rendering process Cons of using NC: Based on the document type definitions = possible to be strongly typed using ModelsBuilder. Nested Content allows us to define element definitions using the built-in document types objects (widely used for documents and page representations in the Umbraco ecosystem) and “nest” them in a defined structure - even nesting other definitions within others. Having Nested Content, (which was merged into the Core back in the day and originally developed by UMCO by Lee Kelleher and Matt Brailsford), we’ve started to see constructions of stacked components = blocks using this property editor. Grid editor, which was already very popular, was available out of the box, but for many developers using it with the built-in configuration and without strongly typed objects within it, was a “no-go” and pure struggle.īefore amazing package creators and community people decided to put more effort into bringing some of the most popular packages to v8, developers were struggling and trying to find a way to replicate the behaviours that they were used to using when they were building solutions using Umbraco v7. When Umbraco v8 was released, one of the first ‘missing’ parts of the project and ecosystem was the lack of package support such as DTGE (Doc Type Grid Editor) and Stacked Content. Let’s quickly review all of them and try to compare to make this choice easier for all of us. It’s always great to have a choice, but it’s also problematic because it throws in concerns and questions like WHICH ONE TO USE IN OUR PROJECTS?! Not mentioning that we’re also aware of the upcoming built-in to the Umbraco core block editor which is going to be released with the Umbraco v8.7, (no target date, but 99% completion state seems to make it a short call!). Perplex released Perplex.ContentBlocks, KØBEN delivered the Bento Editor and many other developers and agencies are currently using their own implementations and approaches to achieve the same goal - to make the editor's life easier when creating rich, grid-based / stacked content creations. ** UPDATED: September 2020, following the Umbraco 8.7 release that includes a shiny Block Editor!**ĭuring the last couple of weeks, we’ve seen a couple of new releases of block-based editors for Umbraco v8.