Understanding FatWire architecture is the main purpose of this lesson.
FatWire is a content centric CMS, so in FatWire everything is considered content, or specifically to FatWire content is referred to as an asset. From this point forward anything created in FatWire or for FatWire will be referred to as an asset. FatWire is broken into two parts: Staging and Production.
This is the development environment, it is here that content is created or uploaded. It is from the staging environment that the FatWire site(s) are managed. There are three basic types of users of the staging environment: webmasters, content contributors and developers. Each of these has there own interface and controls. These interfaces and controls will be covered in a later lesson.
This is where content is published to. Once on production it has been approved and is available for the site visitors to see.
As I have previously said almost everything in content server is an asset. Specifically they are an instance of type asset. In FatWire a page is an asset, so is an image, an address or a name.
An asset has metadata & attributes, there are some standard ones such as name or createddate. You can also define your own attributes if you wish, such as contributor or colour etc.
Due to the manner in which FatWire is set up you can also have assets as attributes of another asset. In the case of a page asset you may have added an image (blob) and another page, in this case the image and the other embedded page are both attributes of the first asset.
I hope you found this useful or if you have any questions don't hesitate to leave a comment or contact support[@]tomred[.]net
I have spent most of my time working on these little bits of logic or snippets. These come from problems or issues I have encountered over the year. These are insights I have researched or provided as code review feedback.
During my time working in consulting I was tasked many times with delivering FatWire sites. I took notes due to the lack of useful documentation at the time. These are the results of those notes made and shared.
I believe the majority of time on a project is spent with the UI. Web is no exception. I have compiled a set of articles covering HTML, CSS and JS with the intention of taking the sting out of this work.
A space dedicated to all those things you need to know beyond writing code. This covers Linux, Windows, Git and SVN among other hopefully useful nuggets.
I picked up some pointers over the years consulting for government and banking sectors before entering a PCI DSS development environment. This section covers aspects like coding, testing, code review and best practice.
Apps is a section which offers access to bits and pieces I have put together over the last few years. This includes Random Password Generator and Base64 Encoder.