Week 3 - CMS Training

So we began our first session of training today with Flatirons. The training was given by Sam, senior developer, who also engineered the system from the get go. It was interesting to hear him explain to those of us who have slim backgrounds in programming just how the system works. He went through a basic, regular document workflow (explained in prev. blog) and began to work through errors that the system would occasionally experience. He then had us begin working directly with the system -- setting our preferences and creating projects to sample the functionality of the workflow.

We were able to set up projects just fine by beginning in Webtop and using its widgets, then launching XMetal and actually editing the xml tags and content. Going back into Webtop, we would then set the project up for review by those designated as reviewers.

Here was one of the major problems that we had to find a quick workaround for: every time we launched Webtop our preferences would not be set. Webtop had trouble saving our preferences, in other words. We discovered that this occurred because our browsers cache was automatically clearing itself out every time we logged on or off our browser. This represented a huge problem because it is a company-wide standard: web browser's caches must be cleared every time a user logged off the Internet. Sam said he would work on the issue and, in the meantime, we could save our preferences in a .txt file and just reload those upon system start up.

I considered this to be an inadequate condition of the system thus far.


Return to HOME page or leave comment below.