For a while now we're trying to capture the essence of WebAssemblyLine and how to explain to people what it is and what it is NOT. It's very difficult...
One way of thinking about the WAL service is that it's a website framework with an open API. It's a website framework, because it gives you tools (CMS) and conventions (code snippets) on how to build your website. It has an open API (application programming interface), because it allows you to plug-in virtually any type of functionality into your website via widgets. And I think a plug-in type of architecture can be treated as type of API.
Another way of looking at WAL is as unified process. In essence WAL gives you:
- a process for managing and building a website - the WebAssemblyLine™
- tools to accomplish it (the content management system)
- a notation and language to describe and prototype a website (grey-screen prototyping and some phrases)
Sounds awfully similar to the Rational Unified Process in software development.
No comments so far
Post your comment
We moderate the comments in order to prevent comment spam. This means that your comment may not appear immediately after you submit it. Please do not submit the same comment multiple times.