Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Silverstripe application flow chart or architecture diagram?

Go to End

2 Posts   3005 Views


Community Member, 1 Post

13 September 2011 at 10:54am

I've been hunting around for an application flow chart or some kind of architecture diagram of how Silverstripe works but can't find one. If there is one, can someone link me to it?

I think it would be very beneficial to have an official one for new Silverstripe developers to have an understanding how it all hangs together. For starters a high level diagram similar to the Code Ignitor one would be great. In fact I suggest this is included on Page 1 of the documentation/manual because "a picture is worth a thousand words".

Ideally you'd also need a few more detailed, separate diagrams that explain the complex parts of the high level diagram, for example explain how rendering a template works or how form submission and redirections are handled within Silverstripe.

My colleage (who has been using Silverstripe for one year) and I (one month) have thrown together a basic diagram of how we think it probably works. It's not complete though. Can the Silverstripe Devs please correct it or make a new official one as to how it actually works? See Google Docs diagram. To edit it just log in and go File -> Make a Copy.

Many thanks

Attached Files

Forum Moderator, 5523 Posts

13 September 2011 at 11:06pm

Edited: 13/09/2011 11:07pm

The whole project will be taking quite a change for 3.0, the manifest and some other core (like configuration) is changing so would be good to document the whole thing before that gets released. Raise this as a documentation ticket on and I can make sure it's assigned for the release.

I wouldn't recommend putting this on the first page of the tutorials.. If you look at the tutorials and how they're structured it's quite basic for the first 3 steps. Unless someone volunteers the time to go through and restructure / write the docs to provide a logical process *wink*