Umbraco Codegarden review and the future
Last week I attended my first Codegarden. It was great to be able to figure out what the fuss was all about. I really enjoyed being able to meet other Umbraco devs and be a part of it all. Rather than go in to all the details, I'll outline some of the highlights.
If you hadn't already heard, here are the major announcements:
- 7.3 beta is out and available to download
- ASP.NET Identity including support for oAuth so that you can login to the back office with your Facebook or Google account for example.
- Load balancing has been updated to work much better with scaling
- Our Umbraco has been given a complete overhaul
- New REST API for Content, Media, Members, and Relations using the HAL format. Here's a bit of reading around HAL: http://stateless.co/hal_specification.html
- Content type editor changes within the back office making all those document types a joy to edit
I think one of the main things to take away from this is that Umbraco want to be able to iterate in a much faster and open manner, releasing earlier versions for testing and review with the community. So, the REST API and Content type editor are examples of this.
Sessions and open space permalink
In my preview I noted some of the sessions which took my interest. As it turned out, there were some great sessions although I felt the urge for some more in-depth talks with more of an emphasis on code. The last day in particular was what I found the most interesting and useful for me. The idea is that the schedule and topics are defined by the people attending. Each person suggests a topic of interest and people go along and discuss where the future of Umbraco lies. Being able to talk directly and in an open manner with others who share similar issues and thoughts was a decent way to provoke ideas and knowledge for the direction of Umbraco and it's community. It wasn't just code... there were also topics around quality of life, communication channels and the future of Codegarden.
Part of what adds to the fun of Codegarden is that it is a 3 day event. Evenings are spent hanging out with other developers and there is enough time to not feel like you are there one minute and gone the next (even if it did go rather quickly).
This year, there was a march through Copenhagen to the meatpacking district where we were able to enjoy the clear night sky with a few drinks and good company. Umbraco bingo was as crazy as I thought it might be and the package competition had a nice comic twist to it.
Until next year permalink
Next year Codegarden will be moving to a new location, and I'm hoping that I'll be able to join you all for more Umbraco goodness. Until then, I intend to get much more involved with the community and start giving back. Following on from the open space at Codegarden around what you would like to see Umbraco achieve in the next 12 months, here are a few that I've come up with for myself.
- I have already logged a number of issues re: Our Umbraco and they have been fixed very quickly (kudos on that), it is a simple process but helps shape things to how you might want them. It's also handy to find some bugs and make Umbraco aware.
- Submit some pull requests and help fix bugs / add new features. #1 : http://issues.umbraco.org/issue/U4-6562
- Attend and present at local events such as umBristol. Presenting is still quite a new concept to me and something which I struggle getting to grips with, I'm sure as I throw myself more into these kind of situations I'll become more comfortable.
- Kickstart some kind of annual event in the South West. There has been a number of people interested in this, it would be awesome if we could make this happen!
- Start creating some packages! Not just for the sake of it, but there are times when we as developers work on a project and it would be good to share some of the more useful custom implementations we have done.
- Write an article for the totally awesome Skrift.io.
- Build a new website for my football team on the latest version of Umbraco and using some of the latest methodologies (e.g. strongly typed models for one). This one is currently in progress and I will be hoping to release this within the next couple of months.
So there you have it, let's see how much of this I can actually complete.