Mike November

Phonetic alphabet for my initials, k?

Viewing entries tagged with 'frontend editing'

Simple frontend editing

Posted by Marcus Nyeholt on 5 November 2010 | 0 Comments

Tags:

There's been some discussion on the SilverStripe development list about some changes coming in SS3.0, one of which will be a frontend editing UI. Of course these plans are very much plans for the moment - the proper work of research, prototyping and putting together a clear set of features for such a UI has only just begun, which everyone needs to keep in mind. The more feedback and constructive criticism that goes into the process from those who develop with SS every day will mean that the end result will be better than if there was silence. Given that I've had an experimental frontend editing module floating around for about 12 months now, I figured I'd actually set up a demo site that people could play with to see my take on things, and what I'd like to see in future

See the demo here - Username: admin password: silverstripe. The db will reset itself once every hour or so, but please don't ruin it for everyone :).

Some things to know

  • Click the "Edit Draft Page" button to edit the content after logging in
  • You can edit the current page's contents, as well as any associated pages being displayed - when outputting a field in a template, it is wrapped in a call to create an editable field if possible.
  • Styles can be defined in stylesheets that will appear in the Style... dropdown - these are prefixed with .wysiwyg- and automatically inserted.

Template modifications look like


    
$EditableField(Content)

Child pages

Just to demonstrate editing other page contents contained in control lists

Title
$EditableField(Title)
Content
$EditableField(Content)

This is available via my github account, but is experimental code for now. This DOES NOT have anything to do with the SS3.0 plans at all - this is something that has been sitting around for a while but may prove helpful in getting people thinking about what a proper solution should have (ie, everything that this doesn't! :)).

0 comments | Read the full post