- Bill Burlein
- Bryan Williams
- Celina Buczkowska
- Daniel Ryerson
- David Ensinger
- Fred Faulkner
- Jeff Brown
- John Kraus
- Josh Durbin
- Justin Pittman
- KC Dunstan
- Mark Daugherty
- Matt Van Bergen
- Matthew Young
- Melissa Geoffrion
- Michael Kang
- Michael Paull
- Michael Chan
- Michael Hodgdon
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Tom Kelly
October 30, 2013 3:30 PM
The AWS re:Invent conference is just around the corner and there are several things our CITYTECH Cloud Managed Services team is looking forward to: 1. New feature announcements. AWS is always in the process of improving their offerings, adding new features as well as enhancing their existing services. As an AWS premier partner, we have gotten a small glimpse into some of the new offerings but are looking forward to all of the official announcements. We will be able to implement many of their features immediately. Anything that gives us the ability to be more preformat and in turn offer those benefits to our customers is exciting.
October 21, 2013 7:51 PM
Inversion of Control (IoC) is an amazing design pattern. IoC aims to remove static coupling of objects from one another at compile time in lieu of run-time resolved, object interactions based on contracts, or interfaces. Apache Felix implements this pattern with its Dependency Manager.
September 30, 2013 4:21 PM
I am happy to announce that CITYTECH has been awarded the APN Managed Service Provider (MSP) competency by Amazon Web Services (AWS). The APN competencies are AWS partner designations, designed to differentiate partners who have developed expertise in specific solutions areas. AWS has worked to set a high threshold for their partners (CITYTECH is one of only 10 global partners to be awarded the MSP competency).
September 20, 2013 3:59 PM
Welcome back! We are diving right back into templates in this blog - if you missed Part 1, go ahead and read it now, and then we'll dive into the code. The Layouts Sticking with the three column layout example, our super basic layout with html looks like the following:
September 20, 2013 2:01 AM
Here at CITYTECH, we are dedicated to providing the best service and the maximum uptime possible for our clients. Keeping customers happy however would not be possible if it weren't for our monitoring solution combined with our application & infrastructure-specific customizations. For us, the top 5 things that have helped are:
September 18, 2013 5:10 PM
CQ is very conscious of the author experience, so what surprises new CQ authors and developers alike is that once a page is created, it is fixed in its template. A two column page stays a two column page, a one column page stays a one column page. That is, unless you’ve got some time and/or sympathetic developers. There are, in fact, two ways to change a template: delete the page and recreate it from scratch with the new template, or take the time and effort to switch the template and map content from the old one to the new one in order to preserve content. Not impossible, but certainly not the best use of time.
September 3, 2013 5:03 PM
Through the last 3 blog posts in this series we have learned what the CQ Component Maven Plugin is, some basic usage of the plugin, and some more advanced use cases. Now it is time to learn how to extend the plugin's functionality so that you can add your own transformers and widgets.
August 28, 2013 8:46 PM
One of the best parts about using Java and annotations to configure your dialogs is the ability to use objects to build nested dialog elements and to reuse pieces of a dialog. Throughout this blog we will use the example of a link object that contains a title and a path. The code follows:
August 27, 2013 9:39 PM
Introduced in the prior post in this series, the CQ Component Maven Plugin offers an idiomatic, annotation-based approach to the development of CQ Components. This post should help you get started using the plugin in your CQ project.
August 26, 2013 3:03 PM
Components, the building blocks of pages in the Adobe CQ Content Management System, are comprised of a number of parts. During development, one often finds oneself creating components by copying and pasting existing components and tweaking those aspects which makes them unique. This is typically easier than writing the parts from scratch as many of the parts, such as the dialog, the component node definition (.content.xml file), and the edit configuration, are XML serializations of JCR nodes and as such are cumbersome to construct. Further, when developing components with more robust authorability requirements, one finds oneself referring constantly to the CQ Widgets API documentation along with engagement in a healthy amount of trial and error in the development of Widget Dialogs. This is largely due to the fact that dialog.xml files are without schema- which means tooling is hard pressed to assist in their structural creation and validation- placing the burden of memorizing, or looking up, the properties germane to a Widget xtype on the developer.
- New Features for the venerable AEM Groovy Console
- Resolution Independence with SVG in Adobe AEM (formerly CQ)
- Five Good Reasons to Use Grunt for Front End CQ Development
- Creating a Custom Content Importer for AEM/CQ5
- CT Tag Manager: A Generic Tag Management System for CQ
- CITYTECH Speakers' Top Session Picks for CIRCUIT, an AEM Developer Conference
- Forecast for Adobe Summit: Sunny and Bright
- More AEM/CQ5 SEO Best Practices: Redirects, Vanity URLs, and XML Sitemaps
- Get Ready for CIRCUIT This Summer - Our Developer Conference
- Resetting the Value of Select Boxes in Safari for iOS onChange