Most CMS software focuses on simplifying a limited base of common demands. This means that you have to adapt to the CMS, rather than have the CMS adapt to you. What you often gain in simplicity with a CMS, you sacrifice in originality or the ability to innovate. EBD is different. It happens to incorporate some features that are CMS-l­­ike, but EBD is best described as a Visual Web Application Development Platform—“visual” because it provides a graphical, browser-based integrated development environment (IDE), “web application” because you use EBD to build code to run on top of ubiquitous web technologies (which does not mean that you are restricted to building “for the Web:” you can use EBD to create a company-wide Intranet portal, for example), and “development platform” because EBD takes care of a lot of lower-level functionality, freeing you to focus on the logic specific to your application, rather than on the logic of your operating system, your server, or your data repositories. EBD is not a CMS per se. The EBD software does not focus on the capture, management, storage, preservation, and delivery of content. However, many people looking for a CMS are really just looking for a way to enhance their web presence or to ease the management of their web content. Some people are looking to run the online part of a business. Some are looking to make their web site more social. With EBD you can do it all because, in short, EBD is software to help you build software and then deliver it with high-speed and scalability. Note: we marked features as “limited” in the CMS matrix to mean that they do not come built-in with the EBD software but can be developed.

Enhancements in version 3.4: support for .NET and ASPX, ability to use Excel files as a data source, WYSIWYG text editor upgraded, better XML editing and syntax highlighting, FTP instructions, enhanced form security (anti-XSRF), new line of widgets, new database transaction control

Enhancements in version 3.3: ACL for administrators, UDDI support, new IMAP instructions, server-side programmatic image manipulation, JSR-254, JSR-168, JSP, introduction of EBD widgets for code packaging and reuse, introduction of EBD packets for the sharing of templates and libraries

Keywords: Apache, Apple, Ajax, J2EE, JSP, IIS, Internet, Intranet, Linux, Mac, MVC, MySQL, portlet, REST, servlet, SOAP, Unix, WDSL, web app, web services, Windows