In the month since I’ve released the first AGS Whitepaper – Grid System, there have been 44 readers who have downloaded the whitepaper. In all honesty, I’m quite shocked (flattered, overjoyed, embarrassed are some of my other emotions) with the amount of people that is actually reading this blog! And here I thought, I’m the only one reading my blog…
With that said, starting today, I’m going to *try* to start updating the blog with a more consistent schedule for the sake of the readers. My plan is to update the blog within the first two weeks of the month (i.e. Day 1-15). I’ll try my best to do this despite the client commitments that I have within those two weeks. We’ll see how it goes. Thanks for reading the blog and feel free to post comments/suggestions.
For this month’s update, I’m releasing an updated version of the AGS Whitepaper – DAM (Digital Asset Managemen Implementation. This whitepaper is intended to assist consultants in their projects specifically for clients that are looking to use the DAM feature of AEM. I’ll introduce the concept of “4 S’es of DAM” (i.e. pronounced as “Forces of DAM” they are: Store, Search, Share & Simplicity). That’s it hope you guys enjoy!
DOWNLOAD NOW (1.1 MB)
AGS Whitepaper, is a series of whitepapers that I’ve written for Adobe Global Services (AGS). The whitepapers were all based on the experience and knowledge I’ve had throughout the various projects/clients I’ve worked with.
The first one that I’m releasing today talks about the Grid System, originally released on 2011 for ADEP 10 (pre-cursor to AEM).
Note that the document originally refers to the 960 grid system (http://960.gs), since that’s what I used for one of my implementation. However, similar CSS grid system frameworks such as the one included in Bootstrap (http://getbootstrap.com/) can be used as well.
Enjoy! More to come!
The Grid System solution can be divided in two parts: First,we define a layout foundation by dividing a CQ page into a series of section/area and columns. Second, using the open-source 960 Grid System (http://960.gs/) it allows us to create a flexible template layout for the pages of the site.
Dear Digital Marketers,
I don’t know how to start this, for writing is usually not my style. But enough is enough. I’d rather say it now so you can understand how much I’ve toiled for the past few years acquiring, developing, and doing everything else that I can so you can enjoy the fruits of your labor, better.
You’ve known me for quite some time now. Perhaps in a different appearance back then compare to now. But you know me. Regardless, it is not what I was before, but what I hope I become to be. Someone that is there for you from the point of creation to the point of realization. Such proposal might be hard to grasp right now, but in time you’ll understand what I’m trying to say.
I can’t promise to you that I have no flaws. But what I can promise to you is that I can be better. For change is the only constant in this world. But change for its sake is pointless; it must be for the better. I hope you realize this more than most. So you can embrace me and realize what you’ve been missing.
Adobe Marketing & Creative Cloud
Considering this is the first “Consulting Wisdom” post of the Wisdom Series, I would like to explain my goal for this category. I’ve been in Consulting for almost six years now, all in the technical field. I don’t consider myself a guru, but over the years I’ve experienced a few things that I can share for everyone to learn from. That is the goal of this series, and I hope in some sort of fashion this may be of use to your career.
At some point in a project (hopefully), you’ll get to what we usually call the “Go-Live” day (i.e. the launch date, the drop-dead day, the D-day, etc) and with that said, I say: CONGRATS!!!
Not a lot of projects reach this point of the game. If your team is one of the few ones, consider yourself lucky. It takes a combination of a good team, a reasonable client and a realistic project for this to happen. However, this eventful day where you turn the switch “ON” doesn’t usually go as easy as it sounds.
Have you heard of Murphy’s Law? Paraphrase in multiple ways, essentially it goes like this: “Anything that can go wrong, will go wrong”. For multiple projects I’ve worked with, Go-Live day and Murphy’s Law usually goes hand-in-hand. It may not be everything going wrong but somewhere along the line there will be some sort of surprise that is unaccounted for. Regardless if you’re not the Tech Lead, Architect or some other leadership role there is one mantra that you should tell yourself:
We are going live today, We are going live today, We are going live today.
Hello folks, sorry for not posting in a while. As always, I’ve been busy with life, work and everything else in between. Going forward, I’ll try to post at least once or twice a month (or else this blog will be archive automagically as I’ve discovered!)
So in the spirit of sharing, I’m starting a new series called: “Wisdom Series“. I’m calling it “Wisdom” more so because much of the post that I’ll be sharing are all real-project experience that I’ve personally encountered throughout my clients instead of just random “knowledge info” that you can readily obtain by searching the docs.day.com or some other websites. Also, I like “Widsom” in general, since it was my class section name back in Grade 5! Ah… those were the days…
For starters, I’ll divide it up into two different categories:
- Tech Wisdom – talks about different AEM specific or other technical info, tricks, etc.
- Consulting Wisdom – talks about different consulting engagement do’s/don’ts, etc.
Anyway, hope I can continue this series going for as long as I can and hope you guys see some use from it.
For the first Tech Wisdom series I’m sharing, it’ll be in regards to the newly introduced concept of “Project” in AEM 5.6. It’s a good concept however there is still much to be desired as far as the current implementation.
Here’s a scenario for you…
“Your mission should you chose to accept is to build a CQ site in four weeks and all you have is a series of design comps”
Sounds fun eh? Well it actually happens in most projects that I’ve been in. You see in most cases clients decide to build a new site in the following order:
1. Client buys CQ/WEM.
2. Client hires design firm to design the new site.
3. Client hire us to implement the site based on the design comps.
So where/how do you start? (That’s usually the question that clients ask us on the first day of the engagement).
Before I go technical here, there’s ALWAYS one thing that should come first regardless of the project: Business first.
So understand what the project is all about, why CQ/WEM was purchased and what is its driving purpose. Project success are measured not by the elegance of the design nor the complexity of the code, but rather meeting (and exceeding!) the expectations.
Once that is clear then it’s a matter of following few simple rules in the “comps-to-components” translation. (Note, it would be easier to follow the instructions below with samples. Unfortunately most samples that I have are client sensitive data, and it’s hard to find samples online).
“There’s no such thing as an ADEP WEM Kool-aid drinker… only pragmatist”.
What in the world am I talking about?
For the “culturally-challenge” individuals when someone is referred to as “Kool-Aid drinker” it means someone who blindly believes in a certain ideology without questioning common sense. For the “acronym-challenge” individuals ADEP stands for “Adobe Digital Enterprise Platform” and WEM stands for “Web Experience Management” (Take note that WEM is one of the solution that is provided by the ADEP platform, it used to be referred as Communique but the marketing team doesn’t like the spelling or something).
Pragmatist is someone who make sense, a realist, or pretty much someone who for all purposes believes that in practice lies the true meaning. I’m a pragmatist by heart, and so far it did me well.
So why do I consider those that admire the ADEP WEM platform as pragmatist? Well there are multiple things but to get started I’ll first explain it by listing out the things that I admire about WEM.
Welcome to my blog!
A quick introduction. I’ve been working with enterprise content management system from Vignette’s VRD system, Interwoven’s TeamSite, and other open source such as Joomla and Mambo. I’ve started website development around 1999 when I launched my own community of music video editors at: www.nkode.net. Ever since then I’ve enjoyed working in this field and I was lucky enough that my career path lead me to one of the top web innovators of today with Adobe Systems.
I’ve been a technical consultant with two other well-respected software company: HP-Autonomy and OpenText-Vignette and one thing that I learn is that there’s no such thing as a perfect content management system. However, (regardless on how bias this might sound) Adobe’s WEM (formerly known as Communique) is perhaps one of the neatest product that I’ve worked on in building websites. What sets it apart from other product is how robust and well-conceived it is. Heck to start, tell me another CMS that has it’s own web-based IDE? But seriously though, the reason why I think ADEP WEM’s platform is unique than all other CMS I’ve worked before is its repository — CRX. The flexibility of having everything in one location creates a very unique system.
Well, enough of this technical stuff… I hope you guys/gals enjoy reading my blog. I’ll try to keep it easy to read, more hands-on examples and pictures (in short… NOT BORING… that’s tough for any tech topic). I’ll be posting topics mostly as it relates to Adobe’s Digital Enterprise platform, however I’ll squeeze in some tech topics unrelated to Adobe but related to some CMS or the overall tech industry.
Redundant as it may be… But again I warmly welcome you to my blog!