Welcome to AgileSites, the Open Source framework for Agile development with Oracle WebCenter Sites (formerly Fatwire Content Server).
The framework is released under the commercial friendly Apache License 2.0.
Read on this page if you want to know more about this framework.
If you already know what is it, then you can:
If you ever developed with Fatwire Content Server or Oracle WebCenter Sites, you may think (as many does) it is somewhat lacking friendly development tools.
As a developer you may have a wish list. I had a wish list too. At some point in time decided to fulfill some of my wishes for Fatwire and Sites development. This framework is the result of this (one year long!) effort.
If your wishes are similar to mine you may be interested in this project.
So, do you want...
thus separating presentation (view) from logic (control) and content (model) ?
coding all your logic in plain Java (using full Java oop and not crippled JSP Java and awkward library CSElements) ?
so it can be updated easily by Web Designer without extensive recoding?
possibly less verbose, more consistent and helpful in preventingsilly mistakes?
thus tracking your work and sharing it with other developers in an healthy way?
so you can develop in Test Driven way and keep a test suite to avoid regression bugs?
integrating and verifying the work of your team, allowing each developer to work in isolation with the JumpStartKit?
that can be easily shared, tracked, compared and deployed?
when you do any change, even small, to your Java code?
either Eclipse, Netbeans, Idea or even Notepad or VI if you like ?
while developing new code using this framework?
being 100% compliant to standard practices
If any of above is in your wish list, then this framework may be suitable for you.
This framework changes the rules of the game in Fatwire/Sites Development.
It modernises Oracle WebCenter Site development providing a layer that introduces a lot of features allowing development in a modern, easier and agile way.
The inspiration of the framework are modern and agile web frameworks like Ruby on Rails or Play! Framework.
This framework is strongly opinionated. It is built based on the following assumptions, or opinions if you prefer (incidentally those opinions are very similar to those advocated by the Agile Development Moviment):
If you disagree with those opinions and think the traditional way of working is just fine, then maybe this framework is not for you.
While changing all the rules of the game, it tries to play fair:
It does not violate any rule written in documentation, especially caching rules (that are still 100% Sites rules) code implementing a site
There is a clear separation integration of the framework and the product. The framework is invoked by standard JSP and the output is still managed by JSP.
As a result you need not to worry of incompatible changes would break the site, since they would affect any other site.
Oracle has not reason to refuse support as long as the question are not specific to the internals of the framework. The framework is a fully documentation-compliant website implementation.
The framework ultimately produces a collections of method calls stored in a single jar that generates strings rendered by JSPs. Everything else is there to ease the creation of such a jar.