Internet World 2012
Tags: EPiServer
Posted by: Joel Williams
We are delighted to be building on our relationship with EPiServer by joining them at Internet World 2012.
Team Auros will be on the EPiServer stand (E5030) to help spread the EPiServer love to all the trade show attendees from Tuesday the 24th to Thursday the 26th of April!
Come and have a coffee with us and chat about the latest EPiServer developments, commerce, social media, mobile, and Instagram being bought by Facebook for $1billion.
It's also worth making a space in your diary for the two EPiServer sessions in the event theatres:
- Fire up your mobile and tablet channels (Tue 24th 13.10-13.40 in the Mobile theatre)
- Consolidating your social media presence (Wed 25th 1045-11.15 in the Social Media theatre)
We're looking forward to making some new friends, see you there!
A review of EPiServer Social Reach
Tags: EPiServer, Social media, Web Content Management
Posted by: Guest Blogger
EPiServer has recently released a new add-on for their CMS platform – EPiServer Social Reach. The add-on is designed to help businesses to manage their social media presence, helping marketers to manage their campaigns across various social media channels from the comfort of the standard EPiServer administrative console.
Umbraco website migration for SYHA
Tags: Alterian, Site migration, Umbraco, Web Content Management
Posted by: Adam Jenkin
We have just completed an exciting project for the Scottish Youth Hostel Association. Their website which used to run on Alterian CMC (formerly Immediacy), now is powered by Umbraco!
This was an absolutely perfect candidate for an Umbraco website migration. Other than being a great CMS for Immediacy customers to migrate too, the project gave us the opportunity to use some of the great add-ons from the Umbraco Community. Here is just a few that really made the job much easier for us.
Bringing the SASS
Tags: Development
Posted by: Stuart Burrows
For a little while now, we’ve been looking into ways to improve our frontend build speed, scalability and maintainability. One of the ways we hope to achieve this is by adopting a CSS precompiler. After reading a couple of online articles, mostly the comparison between LESS and SASS, we chose the latter. I personally feel it offers a solution which is more in line with my own perceptions as well as being entirely suited to our needs.
What’s Sass / what’s the point?
Some of you may be familiar with SASS or LESS but for those who aren’t the point is simple; CSS is limited. Since styles first started to cascade little has changed in the language. “That’s nonsense!” I hear you cry, “We have had multiple layers of CSS released and there is so much in CSS3 we could have only dreamed of back then!”. True but on a fundamental level the way we write CSS has barely changed at all. If anything CSS3 (and the haphazard adoption process) has only highlighted this issue. So while we can do so much more with CSS now than ever before, the way we write it hasn’t changed. Is this a problem? Well, strictly speaking, no. There is nothing actually broken here, it’s just inefficient 1. SASS is a CSS compiler which introduces variables, reusable chunks of code and some basic functions. The net result is that you should end up writing less code that is more easily maintained. For me this functionality is the logical progression from cascading styles and I felt that SASS, rather than any other CSS compiler, suited our needs best. If you doubt the benefits of this language try writing your next large javascript functions sans variables. Possible, but unpleasant.
