Publishers of technology books, eBooks, and videos for creative people

Home > Articles > Web Design & Development > Adobe ColdFusion

Initial Thoughts on a ColdFusion MX Content Management Project

  • Print
  • + Share This
Sit in with the folks at fictional XR Solutions as they plot out a strategy for a content management project.
This chapter is from the book

The folks at XR Solutions make a point of evaluating clients and applications individually, resisting the urge to try to solve every problem with the same solutions. As J.P. Levine, the CEO, too often reminds his team, "If all you have is a hammer, every screw looks like a nail."

J.P. assigns the EduHealth content-management project to Mark Foster, a senior development manager who is just wrapping a project for a local government agency. Team members are assigned to projects by the development manager on a project-by-project basis. XRS finds that by mixing the team makeup, individuals are exposed to a greater variety of skills and talents, and can thus be more creative in problem solving.

Mark emails J.P.

EduHealth team
Email
Date: July 3 To: J.P. From: Mark Foster Subject: EduHealth team JP, Wanted to get this to you before you took off for the 4th. Here are my team preferences: Teri Martin Vijay Singh Sam Carlson Al Sharpe (I am assuming he'll be with us the whole summer, right?) I'll meet with them when we get back after the break. Mark

The next day, while most of his coworkers are enjoying beer and barbecues, Mark reads up on the notes and requirements obtained by Maria Chavez in sales. He scribbles and doodles all over the printouts, and prepares for the first team meeting.

With J.P.'s approval (and verification that Al is staying until the start of the next semester) the team meets the next day.


MEETING NOTES

Present:  Mark Foster, team lead
          Sam Carlson, developer
          Teri Martin, developer
          Vijay Singh, database administrator
          Al Sharpe, intern

Mark reviews Maria's notes and then launches a buy-versus-build discussion. All are in agreement that any bought solution would be overkill, since this is a simple app and doesn't need all the features and overhead of a commercial content-management systems. Plus, any commercial system would place additional burden on users, and it would be too hard to create a simple interface that provided only the needed functionality.

Sam hands out copies of the kind of content (articles) that's typical of what EduHealth creates. Most of the content consists of text, and there's no standard structure for the most part. Teri says that based on her experience, the folks at EduHealth probably have no idea what they really want—and won't until they see a finished product and figure out what they don't like. Mark agrees, and says that's why whatever we create needs to be flexible and structured properly.

Al asks for an example, and Mark draws something like this on the whiteboard (see Figure I-2.1):

I-2.1I-2.1

The screen scribbles show different ways to present the same information. If the screens are designed properly, using data in different screens is just a matter of presentation, and underlying data is not affected. Mark has an email message he wrote for a previous project on separating presentation from content, and he will circulate it.

Vijay says that database design is most of the work. (He always says that.)

Sam mentions that he wants a rules engine. It's not part of the specs, but it will allow for additional features later on, when they are needed. Those features could include the following:

  • Show content on certain days
  • Show different content by time of day
  • Hide or show specific articles based on source of request Mark thinks a rules engine may be unnecessary; Sam will investigate what would be involved.

Action Items:

  • Mark to send out copy of e-mail
  • Sam to look into rules thing
  • Vijay to research database schemas used in other projects

Meeting adjourned.


With the unanimous decision to build a custom application, Mark meets with Maria and J.P. to bring them up-to-date. Maria says she'll talk to David (Dave) Keyes at EduHealth and asks if she can schedule a meeting for next week to present a formal proposal to the EduHealth people. Mark agrees but asks Maria to articulate that at this point the team will concentrate on functionality and not on a pretty interface. Maria nods.

Separation of Presentation and Content

Mark sends out an excerpt from e-mail he saved in his Really Good Stuff Worth Keeping folder. The gist of it is this:

The biggest problem facing most developers (both static-page designers and application developers) in the Web space is that they routinely mix presentation and content. Consider the following:

  • Web pages contain content and HTML formatting in one page. This makes reusing that content with different formatting very difficult, essentially requiring all formatting to be manually removed and then reapplied.

  • Application pages—written in ASP, Perl, PHP, Macromedia ColdFusion, and so on—usually contain database calls, conditional processing, output formatting, form validation, and more. So a change in database design, for example, necessitates all sorts of code changes.

  • Whoever creates a Web-based application design needs to know SQL and database layout. Similarly, whoever works on basic business logic needs to know about data presentation. And so on. This is not scalable at all, and this kind of cross dependency does not allow development teams to grow and work on more complex projects—developers should be able to concentrate on what they do best, not spend time brushing up on stuff they don't need to know.

Structured development requires breaking applications into tiers or levels. At a minimum, the content and presentation tiers must be separate: Content must never be tied to presentation, and presentation must never be tied to content.

NOTE

The content tier isalso referred to as the data tier.

For example, if the content in a database was going to be displayed in an HTML Web page, a Macromedia Flash movie, or a wireless application protocol (WAP) device, and rendered in PDF format, the content should always be the same. Only the presentation should differ.

Similarly, the presentation code that generates HTML output should be able to do so for all sorts of data; it needs to be reusable too.

Developers refer to this issue as separating presentation from content. There are lots of different technologies and buzzwords used to accomplish this, but all seek to do the same thing.

Al instant messages Mark:

Al: Sounds like an added level of complexity.

Mark: Not really. If done properly, it's actually less work and less code.

Al: Where can I see examples of this?

Mark: Look at the CFC files in the project we just finished. Try user.cfc and catalog.cfc; both are good examples of encapsulating data and supporting code into black boxes so that presentation code can concentrate on presentation and not have to know how users and products are stored in databases.

Al: Thanks, will grab those right now.

Mark: Enjoy. Oh, and FYI, CFCs are a great (and simple) way to make all this work. You might want to play with those.

Al: Will do.

Al opens the user.cfc file and scans the code. He has never used Cold-Fusion or CFML before but the syntax is easily read and the code well commented—he has no problem getting the core concepts. He makes some notes for future reference:


All database calls live inside an object.

The object exposes methods like "Get" or "List" or "Add."

Methods take arguments.

Methods return data.

All processing lives inside the method.

Methods can be called by presentation code without having to know about how things work internally.


Al looks at some of the presentation code and notices that the Get user method is used all over the place in all sorts of user interface (UI) code, and none of the code knows that the data is being pulled from a LDAP directory. Suddenly it all clicks. He fires off another instant message:

Al: I. get it! I'm a believer!

Mark: Glad to hear it There's hope for you yet. :-)

  • + Share This
  • 🔖 Save To Your Account

Peachpit Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Peachpit and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Peachpit products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email ask@peachpit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by Adobe Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.peachpit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020