IdoNotes (and sleep)

ILWWCM Days #2 and #3

Some areas went quite well as we deployed and customized more components, content and areas of the site.  Other areas were not quite so lucky.  Read back a couple days if you missed the posting on Day #1

Unlucky

• The search never did work right.  Even the demo site that comes gave the exact result we were getting.  I took this as a good sign that we created the necessary components and design, but something on the server end wasn't acting right.
• Next up was the dynamic menus.  They are supposed to build as you go along and change as you modify site areas.  With the proper filters they are quite powerful.  Now they do eat more resource than some navigators, but you have to weigh which one is appropriate for your usage on the site.  We had some trouble getting the menus to appear at first.  Even after going back over the config about 3 times.  Then they just suddenly appeared.  Wierd.
• Not enough error checking.  You are able to type in forms, components and other items even if they are spelled wrong or do not exist.  Sure, that is good while building, but something information at least would be a benefit.  You try to paste as much code as possible that you grab from other places, but when entering new, it is up to you to recall "/> is the way to close certain tags.
• The desire for multiple instances of the same document in draft status while in workflow.  We found instances where this would be appropriate.
• The constant refresh necessary bit us more than once today.  Sometimes you have to entirely close your browser because even though you can see it in the view, ti won't show in selections.  Restarting the browser takes care of that.

Lucky

• The power of the software showed through today as we applied workflow and pushed pages to "Next Stage" throughout the machines.  The site administrator can come in at any time and move things along if necessary which is a nice touch.  In case someone takes their time or even goes on vacation.  Of course, a timed stage could be used, but it was not appropriate for the workflow we were building.
• Browser-based work for most everything (outside of developing Java and other components) makes life easy
• The template based approach makes changing entire sites awesome.  The ability to change the template on the fly works great for testing.
• The stages that wrap security inside make working with drafts nice
• The ability to grab a component for a full page layout/design or randomly pull components in as content on pages.  That allows some cool things to be tossed in where needed
• The dynamic and content driven navigators!!  I can't say much more there.  If you format them properly, they give off some stunning effect.  Plus as site areas change, you never had to go back to the navigator component and update unless you are providing some filtering.
• Version control and the ability to push a version back into production
• The ability to manipulate multiple sites and share some common components and design all at the same time.
• You know, there is some more but wait for tomorrow's posting on this.

blog comments powered by Disqus



On Thursday, June 16th, 2005   by Chris Miller        

Next Document | Previous Document