Support > The neatComponents Guide neatComponents runs as an entirely web-based service, on Windows 2003 Server.
|
Why is this important?
- Local machines don't need to be as powerful - keeping costs down.
- Local machines don't need individual licenses for design software - keeping costs down and making deployment of editing functionality to a wide rangle of users practical and affordable. In extranet environment you can even allow external users restricted editing permissions.
- The system can be updated centrally - server updates to the editing software automatically update the behavior of all editing - saving costs for product rollout.
|
|
|
Website management the hard way
Most web design systems require you to use client-based software (Dreamweaver, FrontPage, etc) to create pages, and then upload them using FTP to the server.
This causes all sorts of problems, not least the hassle of managing the rollout of the client software to designers, and the cost of acquiring the necessary licenses. |
neatComponents makes it easier - and cheaper
neatComponents provides a full editing and design interface via a browser, so there is no need to install software on the client machines. Normally this would mean that the editing interface is 'clunky' and restrictive in what it allows, but the neatComponents interface is designed to allow you complete flexibility over the design and structure of the site, and great care has been taken to present an interface that looks as much like a local application as possible.
Naturally there are some specialist tasks better done on a locally-hosted application - making Flash animations or graphics, for example. These can then be easily uploaded to the site for display. | 
