Google Web Toolkit (GWT) was optimized for working with a Java Application Server (Tomcat, GlassFish, Jetty, etc) as a back end. But, there is no reason you can't use GWT any of a number of other environments.

LAMP (Linux, Apache, MySQL, and PHP) environments are ubiquitous on the internet. This project seeks to combine the development power of GWT with the availability of cheap LAMP hosting to create a fast and simple CMS.

Why GaSP?

Because it sounded better than GAMP? :)

Not quite. GaSP is an acronym for GWT, SQL, and PHP. Though I used MySQL, the queries used are so generic that porting GASP to any SQL (Postgres, SQLite, Oracle, MSSQL, etc) is a simple task. And, since it should run without a problem against any web server (not just Apache), one could argue that the proper spelling should be GaSP. And, since writing this, I've tested it against a few other web servers. So, now that I know it works, the spelling has indeed changed to GaSP.

GaSP's first project is the Web Engine (a CMS/Blogging system). Other projects following the same design principles will follow.

Current Features

• Flexible pure HTML design (Designers just place the IDs for widgets into their layout, GASP does the rest)
• All widgets are optional (Don't like a widget? Don't use it!)
• Crawlable AJAX design (Static HTML Snapshots are served up for Spiders and Bots to help with indexing)
• Integrated Google Sitemaps
• Integrated SAPTCHA anti-SPAM system
• With Ping-O-Matic automated post alert system
• With CKEditor to provide WYSIWYG editing
• With KCFinder as a File Manager
• With NiftyPlayer for playback of MP3 media
• Automatic generation of RSS feeds
• Automatic generation of unlimited (iTunes ready) podcast feeds