Here we go again! Show your support by nominating SilverStripe CMS in PacktPub's annual Open Source Awards.
Your nomination will help us to secure our position as a finalist, which in turn allows us to secure money we can devote on furthering our open source project. Gaining a good position in the PacktPub awards also helps us to spread awareness of SilverStripe CMS, which fuels adoption and encourages growth in our developer community. All this adds up to making SilverStripe an even better CMS!
In order for websites to remain relevant and useful, we believe it's important to usability test them on a regular basis. We don't only recommend this to our clients, but we practice it too.
It's been just over a year since we redesigned silverstripe.com and the best way to check whether it's meeting the goals of our users is to usability test it. We're planning to do this over the next couple of months, initially via a short questionnaire and then with face-to-face interviews in Wellington.
In late July we'll be asking interested users the reasons why they visit both silverstripe.com and silverstripe.org and for details of what they're looking for when they're there. In August we'll be inviting test users to come into the SilverStripe office in Wellington, where we'll run through a series of scenarios to test how they navigate through our sites, and we'll then explore areas that could be improved.
After collating and reviewing all the results we're hoping to better understand exactly what our users (you guys!) want from our sites and how they should be structured to make them as user-friendly as possible.
We're interested in talking with a range of users, including developers, designers and clients. If you're keen on participating then please contact Julian (J) Meadow, our resident usability testing expert, and he'll send you more details. Those that participate in both stages will be rewarded with an iTunes or book voucher.
Of course, anytime you have feedback on our sites you are always more than welcome to let us know by filling in a feedback form, which can be accessed via the the footer on both sites. We really appreciate your comments, so keep them coming!
We'll keep you posted on progress over the next couple of months.
Thanks to everyone who came along to our June meetup in Wellington. We hope you enjoyed your well-deserved beer and learnt a thing or two! We were treated to two excellent talks from Sam Minnée and John Milmine. Here's a quick rundown of what they spoke about, with slides and videos for those of you who weren't able to make it.
SilverStripe CEO Sam Minnée spoke about the technical improvements being made to the ORM in SilverStripe CMS 3, explaining how it will improve performance and reduce the code needed to get information in and out of your database.
This is a guest post from Aaron Brockhurst at Covenant Solutions, who have been doing great work connecting SilverStripe to Facebook.
Social media marketing is growing at a tremendous rate, as more and more brands embrace Facebook and Twitter as a means to raise their brand presence online, and increase business revenues from these marketing channels.
There are a lot of questions we're asked quite frequently about SilverStripe, so we thought it might be a good idea to start addressing some of these through blog posts. This is number two in an ongoing series.
With all our talk about SilverStripe 3.0, people want to know what the implications are for older versions. On Twitter, @terryapodaca asked:
It's wintertime (at least here in the Southern Hemisphere), so the ideal time for reading a good book by the fire – or at the beach for the lucky ones north of the equator. And of course it's hard to find a more thrilling topic than SilverStripe!
Packt Publishing has just released a new book for everybody interested in the topic: SilverStripe 2.4 – Module Extensions, Themes, and Widgets, written by Philipp Krenn. Philipp has been involved with SilverStripe for a while, starting with building our first database abstraction layer during Google Summer of Code 2007.
With the release of SilverStripe 3 preview 1, Sapphire is to be independent of the CMS, to really unleash the full power of the framework. We believe that Sapphire can be used to build much more than just traditional content managed websites - and we're not the only ones who are thinking that way.
Sapphire has also been embraced by OceanBrowser, a Dunedin company who make OB3, a web app for learning that is based around the social media model.
As part of the recent CMS Expo in Chicago, we held SilverStripe Awards to celebrate the amazing work being done by our community. We encouraged everyone to enter, and were thrilled that there were nearly sixty entrants for the eight categories.
The awards were judged by a panel independant of SilverStripe Ltd, and were announced at the end of the expo. Awards were given to companies from Europe, the UK, USA, Canada and New Zealand - a good spread around the world.
It is with an enormous sense of pride, excitement, nervousness and relief that we are able to announce that SilverStripe 3.0 preview 1 has been released. This release is mainly focused on the separation of Sapphire as a framework from the "cms" module, as well as starting the new user interface implementation for the CMS. While most of the work is "under the hood", you should get a feel for how we plan to improve the authoring experience with the new interface.
Note: This release only supports the latest versions Google Chrome and Firefox, we’re in the process of adding IE support.
SilverStripe is introducing "preview releases" as a way to provide interested developers with an early stage snapshot of our work. Preview releases will be followed by "alpha releases", which contain most major API changes, and allows us to stabilise any API changes.
In March 2011, we tested the content-authoring interface within SilverStripe CMS against various major browsers, in order to provide recommendations to our users, and to identify opportunities for improvement.
The testing covered how both performance and functionality within the CMS worked.