PDF Prototypes: Mistakenly Disregarded and Underutilized

We are all familiar with PDF documents, but I found this article in Boxes and Arrows very interesting. It has never even entered my mind to create a clickable PDF to prototype a new design concept. The article talks about adding dynamic elements to a PDF, using a PDF to mimic Ajax-like functionality to prototype a page-based application like a check out form, and including multimedia in a PDF. The author even goes on to provide the "how tos" for the reader. Check it out at http://www.boxesandarrows.com/view/pdf-prototypes. You have to scroll down the page to get to the article. It looks like the Web page isn't displaying properly. I hope you learn something new as I did.

Content management

Hi Holli.
I have been in the same boat for several years. I have loads of general and project descriptions in word files but no database. I was initially encouraged by one product, RFP Master. It was part of a very expensive suite of proposal software. I am not a fan of "create an instant proposal" software because I do not think they work for my services. But the RFP Master was to provide a location to which you could upload word descriptions and then search through the data. And the price was not terribly bad for the one piece. Unfortunately, it does not behave very well (without the mother ship$$ I imagine) and I am having a heck of a time getting around things. I gave up as it was taking too long and the search was not returning anything. My plan is to create my own database (in time hahahah). Please let me know if you come up with a good plan.Ruthmeri

Content Inventory- Where to start?

One of the biggest items on my list of projects is to organize my company's files into some sort of system. Initially, they told me they wanted to "go paperless." After asking some probing questions, I realized that what they really meant was "get organized." I'm still figuring out what exactly to call this project: Document Control System, Content Management System, or something else? Once I get a grip on what type of information we have and how we use it, I'll have a better understanding of what we need to do to make work flows more efficient. Maybe then I'll know what to call the project.

Has anyone else started a similar project from the very beginning, as I am, surrounded by thousands of crazily named files in multiple unorganized versions?