• Information Architecture, Project Management, and Documentation

  • Skills aquired over time and work history. Download

  • Hands on experience building 50 commercial websites, web 2.0 applications, and personal sites.

  • Web 2.0 commercial and personal sites for over 50 large and small customers.

  • Software developer

  • Web software draws upon skills, themes, and topics, from many disciplines

  • business cards, letterheads, brochures, annual reports, and posters

  • All business types: letterheads, brochures, reports, posters and Business cards.

  • Illustrated drawings, comics, and sketches

  • Character Designs, Logos, Comics, vector images, Blog Themes, Illustrations

  • Jeff Knooren

  • Hey, want to see what I've done in the past? Peek at the RESUME.
.:|=[Content Management System]=|:.

  • CMS Overview

  • Programmed in Coldfusion, Compugasm built a content management system from the ground up. Most CMS applications are the domain of engineers. This applications features were geared toward novices who have little interest in code.

  • It worked exactly like Blogs of today; Using a series of templates to create new themes for websites.

  • Timeframe: 5 months

  • Price: $38,000

  •  

  • Development Issues Solved

  1. Good Customer Experience was the top priority. The interface was designed specifically for easing the workload of employees. It was a great sales tool to potential customers, who were looking to take the drudgery out of report generation.

  2. Architect a complex piece of software through the planning, coding, launch phases.

  3. Scalable framework allows very heavy usage, running on UNIX and Windows systems simultaneously.

  4. Naming conventions on Hundreds of relational database tables needed to be mapped and quantified.

  5. Map application flow, and wireframe and prototypes of final application.

  6. Debugging and work around programming errors, or technological limitations. Linux did not have a great way to display dynamic reports, and with a financial application, reports and summaries were critical features to understand the mountains of data. Involved debugging and testing of thousands of files, and lines of code.

  • Direct Code Access

  • Thought was put into how to control the CMS from a code view if access to an interface was not available. As you can see, boolean values that follow logical naming conventions are used to enable/disable features.

  • Proper naming conventions

  • The problem with icons

  • One thing learned in this interface; is that icons look nice, but they aren't always obvious in function. Therefore, you need to design them properly. I set up an icon matrix to make creating new icons easier.

  • Skinning

  • Pictured here is how changing one variable [Lemon], switches the site color theme, as well as border graphics around tables/DIVs. Of course there was a browser based way to change that option. But thought was also put into how someone coding the application could quickly make changes, without being forced to use a much slower interface to accomplish the task.

  • Public website

  • Client facing website

  • Screenshot of two themes compared side by side.

  • User Interface

  • An output of table information, displayed in a list view. The icon with a page and magnifying glass represents "detail" so you could drill down into a record, and show a more detailed view.

  • User Interface

  • Development Issues Solved

  1. Good Customer Experience was the top priority. The interface was designed specifically for easing the workload of employees. It was a great sales tool to potential customers, who were looking to take the drudgery out of report generation.

  2. Architect a complex piece of software through the planning, coding, launch phases.

  3. Scalable framework allows very heavy usage, running on UNIX and Windows systems simultaneously.

  4. Naming conventions on Hundreds of relational database tables needed to be mapped and quantified.

  5. Map application flow, and wireframe and prototypes of final application.

  6. Debugging and work around programming errors, or technological limitations. Linux did not have a great way to display dynamic reports, and with a financial application, reports and summaries were critical features to understand the mountains of data. Involved debugging and testing of thousands of files, and lines of code.