content-managementfatwire

What is fatwire from programmer perspective?


What open source toolkit does fatwire compare to and are there some particular advantages to fatwire?

How hard is fatwire to export out of and move to a free alternative?

How stable is it as a platform to write java extensions on?


Solution

  • From a development persepective, FatWire can be unfriendly. Having worked on a number of sites using this application it can easy bloat, and become difficult to maintain.

    From a user perspective there has been alot of effort in the UI and this has led to a highly functional tool.

    From a client perspective all clients bar 1 (a large news agency) were happy with the end result. FatWire can slow when using complex logic to generate menus or breadcumbs for example or when you have a large amount of content. This is the main reason the one client was unhappy. The FatWire site regularily struggled under the load. It sometimes seen as a solution to all web needs.

    As such FatWire succeeds in serving Static Content & Semi Dynamic content, but can flounder when forced to do fully dynamic sites (from my experience).