9 Tips to Planning and Building Maintainable Grails UIs. How can we build user interfaces using GSP that are manageable and easy to update?
Many of the books on Grails focus on the technology available in Grails, but very few give rules and techniques to make GSPs manageable. Grails templates and the out-of-the-box functionality is great. But once you start trying to integrate layouts and designs for real world websites, you’ll find that bad coding practices can quickly lead to a chaotic and unmaintainable mess of spaghetti code. In this post, I want to share some tips, lessons and ideas I have learned from projects worked in the last year and a half of Grails UI development.
Planning Your UI 1. For one of our projects, we made the mistake of giving a PSD template to an HTML/CSS contractor. If you’re starting a new project and are not very familiar with Grails, spend a bit of time learning and educating your team about how to properly use Sitemesh layouts, codecs, tag libraries and templates. 2. Are you going to use Ajax? 3. Coding Your UI. Holy Grail of eCommerce Conversion Optimization - 91 Point Checklist and Infographic. Spring Security Core Plugin 1.2.7.3. (Quick Reference) Authors: Burt Beckwith, Beverley Talbott Version: 2.0-RC2 The Spring Security plugin simplifies the integration of Spring Security (formerly Acegi Security) into Grails applications.
The plugin provides sensible defaults with many configuration options for customization. Nearly everything is configurable or replaceable in the plugin and in Spring Security itself, which makes extensive use of interfaces. This guide documents configuration defaults and describes how to configure and extend the Spring Security plugin for Grails applications. Release History and Acknowledgment This plugin is based on work done for the Acegi plugin by Tsuyoshi Yamamoto. 1.1 Configuration Settings Now in Config.groovy The Spring Security plugin maintains its configuration in the standard Config.groovy file.
This structure enables environment-specific configuration such as, for example, fewer structure-restrictive security rules during development than in production. 1.2 Getting Started No HQL Or: What is DevOps? Update 1: Wikipedia now has a pretty good DevOps page Update 2: Follow-up posts on the business problems that DevOps solves and the competitive business advantage that DevOps can provide.
If you are interested in IT management — and web operations in particular — you might have recently heard the term “DevOps” being tossed around. The #DevOps tag pops up regularly on Twitter. DevOps meetups and DevOpsDays conferences, are gaining steam. DevOps is, in many ways, an umbrella concept that refers to anything that smoothes out the interaction between development and operations. What is DevOps all about? DevOps is a response to the growing awareness that there is a disconnect between what is traditionally considered development activity and what is traditionally considered operations activity.
As Lee Thompson and Andrew Shafer like to put it, there is a “Wall of Confusion” between development and operations. Operations folks tend to come from a mindset where change is the enemy.