Obtaining Alfresco Web Content Management (WCM)
People have been using Alfresco to manage web content since the early days of the product. In 2007, Alfresco released its formal web content management functionality that added features most people expect when they think of a Web Content Management (WCM) offering, including templating, site preview, snapshots, virtualization, and deployment. WCM is a specialized subset of the larger Enterprise Content Management (ECM) umbrella that is focused specifically on authoring, managing, and publishing files used to produce a website.
In this article by Jeff Potts, we will discuss how to create a web project and define web forms using XML Schema to allow non-technical users to create content.
Read Obtaining Alfresco Web Content Management (WCM) in fullMigration from Apache to Lighttpd
In this article by Andre Bogus, we will be focusing on migrating from Apache to Lighttpd web server. Lighttpd is the perfect solution for every server that is suffering load problems, as it has a small memory footprint compared to other web-servers, effective management of the cpu-load, and advanced feature set, such as FastCGI, SCGI, Auth, Output-Compression, URL-Rewriting, and many more. Apache is still the most common web server used today, so while we wait for Lighttpd's world domination, the migration from this server warrants its own article. As this article is on Lighttpd and not on Apache, it assumes some knowledge of the Apache configuration. If anything is unclear, the Apache documentation at http://apache.org/docs/ will be of help.
Read Migration from Apache to Lighttpd in fullResource-Oriented Clients with REST Principles
Resource-Oriented clients are client programs that consume services designed in accordance with the REST architectural principles. The key REST principles include:
- The concept of resource (for example, a document is a resource)
- Every resource given a unique ID (for example, document URL)
- Resources can be related (for example, One document linking to another)
- Use of standard (HTTP, HTML, XML)
- Resources can have multiple forms (for example, status of a document, updated, validated, deleted)
- Communicate in a stateless fashion using HTTP (for example, subsequent requests not related to each other)
In this article by Samisa Abeysinghe, we will study how we can implement clients to consume those services. We will use a real-world example, the simplified library system, to learn from scratch how to design clients with REST principles in mind.
Read Resource-Oriented Clients with REST Principles in fullPlanning Extensions in TYPO3
In this article by Dmitry Dulepov, we will discuss why planning an extension is important and how to plan an extension. Planning issues related to web development are covered in depth in many specialized books. Here, we will cover planning only with regard to TYPO3 extensions.
Read Planning Extensions in TYPO3 in fullA Simple Pocket PC Application using Visual Studio 2005
This article by Dr. Jayaram Krishnaswamy teaches how you may create a .NET Compact Framework (CF) 2.0 forms application. This can be used with Pocket PC 2003, or later devices. In the absence of a device being available for testing, the emulator is the next best thing. The application will be tested on one of the many emulators available in Visual Studio 2005. You may try other devices as well just by choosing the item in the Device Emulation Manager described in the article.
Read A Simple Pocket PC Application using Visual Studio 2005 in full

