Finally it´s June 6 – that means barcamp-time ! We will cover the barcamp by using the official hashtag #AEcamp, posting photos on flickr frequently. After the barcamp we will upload videos of the sessions to http://www.youtube.com/GenticsVideos. And don´t forget to check http://aloha-editor.org/barcamp/

The Aloha Editor Barcamp 2013 team would like to thank Ektron for their support as a diamond sponsor for Aloha Editor Barcamp 2013 in Vienna. A two-day event taking place on 6-7 June, Aloha Editor Barcamp is an annual gathering of people who were working on, with and around Aloha Editor to share ideas and project work.

As a diamond sponsor, Ektron will supporting one of the most important popular parts of the Barcamp – the social event that provides the perfect opportunity for sharing ideas and networking after the day´s sessions.

As the CMS platform of choice for more than 3,800 companies around the world, Ektron enables organizations to create, deploy and manage enterprise-scale, global, personalized websites. With Aloha Editor integrated as default editor, authors can create and edit content instantaneously and see exactly how that content will appear on the website during authoring. The editor provides Ektron customers with numerous benefits, including the ability to easily format text, set hyperlinks, insert imagery, create tables, and copy-and-paste content from Microsoft Word with all formatting intact.

With the Front-end Editor plugin you can start editing your content while browsing your website. No more forms required. Just edit!

Search for Front-end or Aloha Editor in the WordPress plugin directory.

Here you can find more screenshots of this WordPress plugin.

A list of all supported editable elements in WordPress is also available.

Follow @alohaeditor on Twitter.
Attend the Aloha Editor HTML 5 editing camp.

It looks like this:

If you would like to integrate the Aloha Editor functionalities into your application you can do so with Aloha Editor UI à la carte. Easy.

After installing the ui-a-la-carte plugin you can define your application specific toolbar as HTML / CSS code.

Don’t worry. It’s easy.

Aloha Editor will now integrate better into your application or website.

Provide advanced inline content editing:

Here you see the Repository plugin in action:

The UI for manipulating a link is minimal. When typing it will suggest you links in your system / data from repositories you can link to.
Learn more about the Aloha Editor features.

Minimal toolbar design:

Try Bootstrap + Flat UI + Aloha Editor UI à la carte yourself at:
http://runtyapp.org/flat-ui/

Follow @alohaeditor on Twitter.
Attend the Aloha Editor HTML 5 editing camp.

Do you know about the new minimalistic CMS systems with inline editing?

“The easiest CMS you’ll ever use. Great for sites with mostly static content.”

Barley — “this-generation content editor”
Selector* — “Make HTML5 editable – without any hassle”
WizzyWig — “Update your website. Code-free.”

Those are all SaaS solutions more or better to say less available right now — you can watch the teaser videos.

There’s an Open Source Software alternative called Runty. NoCMS

Runty. NoCMS — web editable. smart content!

With the Aloha Editor block functionality it’s possible to trigger actions.

Here: Display tweets related to “Moby Dick”.

CSS3 / HTML5 layout editing made simple. No forms required.

Download  Runty and include this script-tag into your HTML:

 <script type="text/javascript" src="./runty/app.php"></script>

To enable editable areas mark the HTML elements (eg: <h1>, <div>, <p> …) with the CSS class runty-editable (eg: <h1 class=”runty-editable”>).

On top you can see the Runty. Toolbar — it is flexible via CSS / JS plugins.

Give Runty. NoCMS a try. Download now for free!

Join & learn! Attend the Aloha! HTML5 editable camp in June in Vienna and learn how to create innovative UIs with HTML5, CSS3 and Aloha Editor.

Get your free ticket now!

It works on your computer, smartphone and tablet.

Just a blogging platform.

Beautiful dashboard.

Markdown to HTML live preview.

A Kickstarter success story!

Join & learn! Attend the Aloha! HTML5 editable camp in June in Vienna and learn how to create innovative UIs with HTML5, CSS3 and Aloha Editor.

Get your free ticket now!

Although requirejs solves the dynamic loading problem, it also brings an unfortunate side-effect with it, which is particularly problematic considering that Aloha Editor is a library that is meant to be integrated into other applications.

The side-effect is that requirejs loads modules asynchronously. This forces applications integrating Aloha Editor to run in a callback. Aloha Editor suggests the following pattern:

Aloha.ready(function () { ... application code ... });

After integrating Aloha Editor into multiple applications I found that this can be very painful because it forces an additional level of indirection. In smaller applications, this could be handled by just wrapping the entire application with Aloha.ready(). In larger applications I found it easier to handle this on a case by case basis, which however litters the code with Aloha.ready()s and other callback mechanisms. Examples of what that looks like can be found in the Aloha Editor bootstrap file (Aloha.trigger).

There also was the problem when Aloha Editor was using an older version of requirejs. This made it difficult to use Aloha Editor in applications that used a newer version. Now that Aloha Editor has updated its version of requirejs, it is the other way round.

Although requirejs provides a feature that allows a library to use its own version of requirejs by rewriting the “define”s during compilation, that’s still less than ideal because it would mean having multiple versions of requirejs in a page (~6kb min+gz each), and it wouldn’t solve the problem for loading the development version of Aloha Editor inside an application (which is where I tend to spend most of my time).

I attempted to solve this problem with r.js, by implementing some hacks that made r.js output, not the concatenated version of the source code, but rather a sequence of document.writes that write <script> tags into the document. This document.write mechanism could be used during development to load Aloha Editor synchronously, which solved both the asynchronous loading problem, as well as the multiple requirejs versions problem. No change was necessary for loading the concatenated script in production since requirejs supports synchronous instantiation of modules when the module was already loaded (which is true in the case of Aloha Editor because you need to include at least the concatenated aloha.js manually via a script tag).

The r.js approach worked, but I wasn’t really satisfied with it. Too many hacks were necessary to make it work. Instead I wrote a minimal AMD loader implementation that encourages a single concatenated script loaded via a plain old script tag to be used in production, while for development a document.write approach is used.

This leaves us again with the problem that people have been trying to solve by using requirejs in the first place. I believe the solution to that problem should not be dictated by Aloha Editor. If an application uses requirejs, it can be solved with requirejs. If an application uses plain old script tags, it can be solved simply by including the right script tags.

If you are familiar with back-end technologies and find yourself working more and more with client-side technologies here is a great list of 125 CSS and JavaScript tutorials to power up your skills by @CreativeBloQ.

Follow @AlohaEditor on Twitter or like AlohaEditor on Facebook to receive selected news about the latest trends on topics like HTML5, CSS3 and JavaScript.

Brian Porter just published a blog post describing how he integrated Aloha Editor in his Play! Frame­work project. Definitely a good read for everyone thinking about integrating Aloha Editor in his or her project.

I am con­stantly need­ing to update sta­tic con­tent in Tem­plates in my Play! Frame­work project, so I decided to inte­grate the Aloha Edi­tor, an HTML5 WYSIWYG Editor.

It is free to use, and they offer an exam­ple of inte­gra­tion an sav­ing with a POST to the server on this page: http://​www​.aloha​-edi​tor​.org/​h​o​w​t​o​-​s​t​o​r​e​-​d​a​t​a​-​w​i​t​h​-​a​l​o​h​a​-​e​d​i​t​o​r​-​a​j​a​x​.​php

Basi­cally all I had to do in the fron­tend was inte­grate the edi­tor as described, and add a class “editable” to the ele­ment that should be editable.

Read the whole blog post …

Brian will post some follow-up posts in his blog regarding his project, so keep following his Blog.

Aloha Editor BarCamp 2013 — HTML5 editing

June 6-7 2013 an Aloha Editor BarCamp — state of the art HTML5 editing — will take place in Vienna.

Learn about contentEditable in HTML5, Aloha Editor, jQuery (UI) and many more related topics.

If you would like to share your know how at a (mini) session or have any question please send a message to rene.kapusta/at/aloha-editor.org

Follow http://twitter.com/alohaeditor, http://facebook.com/alohaeditor or this blog for updates on this event.

Register here for a free event ticket.