![expressionengine grid field type development expressionengine grid field type development](https://openforis.org/wp-content/uploads/2022/02/image-37.png)
Shortly after Packet Tide acquired ExpressionEngine they announced that Twig would potentially be supported, but the community didn't know exactly what that meant. Even for the most seasoned ExpressionEngine developers, the parse order could make a seemingly simple task an afternoon of work. Unless you had a firm understanding of how it worked, it was often a brick wall for some people. As soon as you needed some complex template logic, the order in which you tried to call template tags cause tags to not work as expected, or simply not render any output at all. "Template parse order" became a well known phrase in the community. Over time though, it started to became it's biggest weakness. Compared to Wordpress' template soup, it was a revelation. It was super simple to learn and you didn't need to know PHP. One of ExpressionEngine's biggest strength, which is what arguably attracted a lof of designers back in the EE1 and EE2 days was it's template language. That is a long list of a lot of new and well received updates.
![expressionengine grid field type development expressionengine grid field type development](https://iue.tuwien.ac.at/phd/ceric/img885.png)
New File Manager with support for subfolders and cloud storage (finally!).
![expressionengine grid field type development expressionengine grid field type development](https://u.expressionengine.com/asset/article-images/cp-grid-field-icons.jpg)