Several questions come up to me consistently while I move from client to client as a technical PM or solution architect. I felt compelled to list my responses to these questions so that you ask yourself the same questions every time you approach a new CQ5 project. MY response questions often lead to longer brainstorming sessions. Here are a few situations.
- Components
- Initial Topic:
- What gets “componentized” versus consumed, integrated or remain separated with regard to CQ5?
- My Response:
- How reusable is this functionality?
- What is the current life-cycle of this development? How frequently is it changed?
- How modular does this need to be?
- Will this functionality be replaced by another CQ effort running in parallel?
- Do authors need to interact with it and set parameters and variables that customize it for that given instance of the function?
- Would exposing dialogs to CQ authors help the website? or confuse the issue?
- How complex do they expect the CQ effort to be? Duration? How does it impact project time-lines and time to market?
- Templates / Design
- Initial Topic:
- How do I simplify my template but allow for flexibility and future growth? How do I effectively use iPar and Par? Should the component be “drag-n-droppable” or called from the template?
- My Response:
- What is the content strategy? How do you expect users to use CQ? Describe the user experience for me.
- What is the product’s feature-set? How will these features be used in the context of the template?
- What is inherited across pages, website sections, domains and corporations?
- How much power should an author have? How do you limit mistakes? How do you reduce error?
- Can the basic layout for several websites be streamlined to support a single layout? Can the differences between 2 websites be configurations on component families?
- Will the template structure be used to mass produce large quantities of websites for smaller units of the overarching website
