I came up with a nifty, albeit jerry-rigged, hybrid Drupal solution that I wanted to share with the local community. If I can make it in April, I will be happy to share the inner-workings.
My challenge is that as lone webmaster for the county, I have my plate full. I spent my first year here deciding upon and familiarizing with Drupal, and, having created several successful Drupal sites now, I am beginning to seriously discern how to rebuild the county's website. As it stands, the site is mostly static PHP (with a common header and footer), and any updates, with a few custom solution exceptions like the HR job listing page, have to be done in Dreamweaver. Ultimately, I plan to port the entire site to Drupal, but I wanted something in the interim that would free my plate as well as prepare me (and appointed county staff) for what it means to open content editing to users via Drupal.
I came up with a hybrid PHP/Drupal solution to take advantage of Drupal's login and content management systems. The gist of it is that for content editing, users log in to to a standard Drupal interface. For content display, however, I expose content via Views via a second drupal site whose default theme is stripped down to bare bones (thanks to this responder) which gets php-included by proxy to the Drupal site on specific pages.
Two examples of drupal-included content is here:
h t t p : / / co.brazos.tx.us/departments/juvenile/employee.php
h t t p : / / co.brazos.tx.us/departments/commissioners/meetings.php
I didn't want to link it directly to avoid unrelated, extra traffic..
Content on both these pages are contributed to regularly by non-tech county staff. This solution, effectively, buys me some time to roll out small offerings to various departments while still working on an overhaul of this inherited site.