Menu

Portfolio/database work

Progress on the stopdesign.com redesign continues. I now have the entire portfolio entered into a sortable, reusable database. I’ve created a bunch of server-side scripts (ASP) to create each portfolio page dynamically based on two templates. One template drives the…

Progress on the stopdesign.com redesign continues. I now have the entire portfolio entered into a sortable, reusable database. I’ve created a bunch of server-side scripts (ASP) to create each portfolio page dynamically based on two templates. One template drives the bulk of the view pages, another one wipes out everything on the page and makes room for a large version. Pieces can now be categorized and sorted any way I like, anytime. Adding a new piece requires absolutely no page editing. Generate a few new images, update the database with new names, sizes, and descriptions, push it live, and the entire portfolio automatically updates. Each page is daisy-chained together to allow browsing through once piece at a time. That was horrid to maintain with the old flat html files, but now, the order and total instances in each category get updated on the fly.

Who said that a designer could never learn practical self-promoting benefits of server-side scripting languages?