W3Ware is NOT to be considered as a competitor or replacement of the traditional HTML editors, BUT to complement of them: these editors usually concentrate on the construction of the content of the pages, they offer much less facilities (automatic support) in areas where W3Ware has proven to be extremely usefull, like:

• the design and construction of the website structure (skelet).
• the navigation within a site.
• the translation of a site in other languages.
• etc.

• Production of an entire website, at extremely competitive prices.
• Speed of development, based on "prototyping" and the concept of "same as except" which allows for the automatic production of a website of at least 75 % of its volume.
• A high quality product (consistent among the entire site, with quasi "zero defects").
• A virtually unlimited list of available options about the website (browser specific, graphical of text-only, static or dynamic web pages, etc, etc.).
• Option to eventually have the organization itself perform a major part of the maintenance of a website (e.g. keeping up-to-date the texts for certain pages specific for the organization).
• Optionally, automatic production of specific webpages like a "site map", a "guided tour", a "disclaimer" page, ...
• Reuse of images which are not site-specific, due to which the effort to produce graphical elements is minimized.
• Reuse of developments performed for other websites by setting special options during the generation process of a website, like "yes or no use frames", "with or without 'onmouseover' events" (to change the color of a graphical element), ...
• Possibility to perform "mass productions", e.g. during the introduction of an intranet when huge volumes of documents have to be converted which all have to comply to certain standards (templates of stylesheets) so that a consistent look-and-feel is achieved.
• Multiple developers can simultaneously work on various components of a website (graphics, textual content, navigation, layout, Java(Script), ...): at the end (or as often as desired) all individual building blocks are assembled together into the ultimate set of web pages.
• Mass-update facilities applied systematically across an entire website (either during the development phase, or after the site becomes operational), like: change in eMail ID, names of subdirectories of the site (like the graphics subdirectory), changed HTML constructs for a specific component of a site (like a shopping cart with changed parameters), change of the physical filename of specific webpages (to be applied systematically across the entire site to point to the new filename), ...
• Differences between the test and production version of a site, like: differences in directory structure, pages that are part of the test version, but not (yet) included in the production version (like the wellknown "under construction" pages), ...
• For sites to be developed in multiple languages (English, French, Dutch, ...), the actual translation (once the site is ready in a first language) can be performed by (less expensive) people WITHOUT any knowledge to build websites (e.g.: no HTML know-how needed), typically by administrative personel or by translators, NOT by HTML writers or Java(Script) programmers. As a variation, translation tools can be used which won't suffer problems because of (e.g.) HTML tags that those tools usually cannot handle without manual intervention.

• Small business accounts, looking for a solution to have a website:
  • at low development costs.
  • with maintenance costs reduced to an absolute minimum.
  • that allows for basic maintenance applied without intervention from the web factory.
• Web factories who want to subcontract the development and/or maintenance of websites to others, because:
  • the cost to develop the website exceeds the amount the customer is willing to pay for it, typically the small businesses websites.
  • the web factory doesn't have enough production capacity, e.g. to setup an intranet for a major account (like banks, insurance companies, ...).
• Web factories who want to take advantage of W3Ware's capabilities may do so, by licensing the W3Ware software from P.H. Vriens bvba.

• http://www.RigoMeys.be: an insurance broker.
• Internationaal Meubelfestival: a fair about furniture, to invite exhibitors and to inform visitors.
• http://www.Herman-Engels.com: a classical music site, dedicated to the yearly calendar of a Flemisch conductor with a reputation that spans all of Europe, and to be considered as a basic web site generated by W3Ware.
• P.H. Vriens bvba: company profile of the developers of W3Ware, including samples of advanced graphical elements.
• shopping.placeto.be ®: an online shopping galery.
• Symposium on Software Reusability: symposium about software reuse, to inform potential visitors.
• Van Poppel NV: a customs office handling all kind of customs formalities compliant to Belgian regulations, including translation of the same site in 5 different languages (80 % of this site was produced by a secretary NOT knowing HTML, JavaScript, etc.).
• aBITmore ® bvba: a webfactory, using W3Ware to build websites.

End of 1998 "Kaasmeester Elsen" was invited to participate in a contest related to the best Flemisch online christmas shop.

... the result of the voting (sequence nr 7 = Kaasmeester Elsen): Kaasmeester Elsen received the highest number of votes.

Afterwards the 3 finalists were further evaluated by a team of 4 e-Commerce specialists from Clickx and Planet Internet, regarding:

1. the look-and-feel (graphics and atmospheer on the site)
2. ease of use (navigation, fast loading,...)
3. The commercial extras (christmas promotions, order- and payment facilities,...)

Result of the evaluation: Kaasmeester Elsen won the "Kerstshop 98 Award", which resulted in additional e-Commerce facilities for Kaasmeester Elsen, worth 100.000 BEF (about 3,000 US $).