Greetings All,
The Institute for End User Computing, Inc. is a New York State based 501(c)(3) not-for-profit corporation pursuing the long term grand challenge goal of designing a new legacy free End User Computing Platform to integrate the best enabling technologies from all areas of computer science and leapfrog today's platforms. Our secondary objectives include educating the public about enabling technologies, public policy issues, and domain specific End User Computing applications, as well as promoting the study of computer science and allied disciplines.
We have a large static website at http://www.ieuc.org which is generated through the use of a rather complex semi-auotomated client side infrastructure that makes use of such tools as Tinderbox, iCal, and Endnote 6. On the server side our site also uses BBClone and phpicalendar.
We want to augment our online presence with a Drupal community that matches the look-and-feel of our existing pages. To that end, we would like volunteers to help us develop some custom Drupal 4.7 modules to encapsulate our existing functionality.
First, we want to create and then contribute to the Drupal Community a model to invoke BBClone's data collection facilities when Drupal nodes are visited.
Second, we are contemplating a much more challenging module to embed Drupal hooks in statically generated non-drupal pages. The idea would be to have our non-drupal CMS generate a call to a Drupal interface php script invoked each of our static pages with that page's globally unique ID. The script would query Drupal to see if that static page had an associated discussion. If it did, it would embed a link to that node in the static page indicating how many comments in the drupal database related to it. It would also create a "discuss this page" link on the page that would load a redirection node whose purpose would be to dynamically create a discussion forum associated with the original static page and redirect the page load request to load that node. This way static content could be controlled and developed outside of Drupal and only those pages with associated discusions would need to represented in the Drupal database, while providing the website visitor with the illusion that the entire site was a single unified system.
Third, we could use some help tweaking our custom Drupal theme to look like the rest of our site. This could also lead to a module with some sort of automatic cross-linking facility to unify Drupal and non-Drupal page navigation or ideally to a module that could automatically import and update cross-linked external XML-based content generated by arbitary client side GUI authoring tools.