-A.J.A.R.-
Most sites I build are super blogs which always have an advertising monetization and social networking and sharing prerequisites. These types of sites have a huge need for external javascript calls to ad servers and libraries by the millions, and can cause a huge lag in page rendering as external requests require a response before rendering the html that follows. The only proven multi-browser solutions for this is to move all external request to the bottom of the site and once loaded, move the content to it's designated location. This method I call AJAR is extremely successful and easy to implement on all browsers for all uses. It is written mostly in jQuery and can also handle cloning existing ads for the use of in-content ads on sites that are AJAX driven. (Example: 'Use AJAX' in Views). An example is Chris Brow's http://MechanicalDummy.com, which I implemented AJAR this way as well as loading externals last. I have created a Module that handles this ability on external calls, called the AJAR modules. This methodology has made it possible for the the site TheYBF.com to even function! It has way too many external requests and if it wasn't for this ability, the sites success wouldn't be what it is in its 30 million uniques multiplied by over 3 dozen external requests. Eventually I will share this module with the Drupal community, but that is a long-term goal, as I have been packaging it as more of an coding standard and methodology than library.
-Recently Viewed-
Recently Viewed module basically connects a cookie to the Views Module. It simply provides Views with a Recently Viewed nodes Filter and an optional Sort override default that makes sure the recently viewed nids are ordered by the way they were chronologically viewed by the user (most recent first). It has an admin configuration page which sets the ability to only track the users nodes by node type as well as cookie settings. Other methods of getting a "recently viewed content" output are not good enough methods and are either a hack, a set of configured modules, and none that I have seen use Views. Views has to be the method of display for this so it can be configured via Views UI, and added as a block easily. This module can be used from for e-commerce stores to real-estate listings sites, and has been a real pleasure to use. It is currently being used in a Manhattan Real Estate site that will be launched shortly.
Basically this CVS application's short-term goal is mainly to provide the 'Recently Viewed' Module to the community. Other projects I have mentioned are still being determined how I plan on maintaining them and if I decide to maintain them at Drupal.org or not. 'Recently Viewed' is also my trial Drupal.org project as all though I promise to be a great maintainer, I don't want to spread myself too thin. Their is noting I hate more than un-maintained abandoned modules!
Thanks for your consideration!
Drupal is the ONLY CMS!
Cheers,
-Joe Weitzel
BOX Creative NYC
http://box.biz
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | recently_viewed.tar_.gz | 2.99 KB | Josephnewyork |
Comments
Comment #1
Josephnewyork commentedRecently Viewed module
Provides Views 2 with a 'Recently Viewed' Filter and an optional Sort override default that makes sure the recently viewed nids are ordered by the way they were chronologically viewed by the user (most recent first).
Comment #2
sunComment #3
avpadernoComment #4
avpaderno