Too much choice! In a popular TedTalk by Psychologist Barry Schwartz "takes aim at a central tenet of western societies: freedom of choice. In Schwartz's estimation, choice has made us not freer but more paralyzed, not happier but more dissatisfied." A choice that many us web developers sometimes agonize over is what web framework to use? Instead of getting into heated arguments about which is better, let's look at it this way: they all can do pretty much the same thing and a user is not going to notice the difference.
History of EntitiesThe very first thing I learned when started working Drupal was this: "everything is a node." This is what allows you to write a module that works generally on nodes and have it apply to sll sorts of content you have no idea about. Later, I learned that this wasn't quite true. It's true that all content types are descended from notes. Comments, users, taxonomy terms are not nodes. They don't share a common base type. In Drupal 7, they sought to resolve this with another level of abstraction called Entities. So the new truth is Drupal 7 is: everything is an Entity.
A paragraph of text. blah blah blah
program code ...
A frequent need we have is to be able generate PDF documents from our website content. A savvy user can always use a print-driver based solution like PrimoPDF to print a web page out to PDF but that's not really user friendly. There are also PDF creation libraries that allow you to programmatically generate PDF output but from my experience they can only generate very basic looking output (and only with a lot of work). That leads me to the best solution we've found from both user and developer standpoints.
Common Look and Feel Standards for the Internet, Part 3: Standard on Common Web Page Formats
For designers and implementors