View allAll Photos Tagged rubyonrails
I'm only throwing this in to show all the steps for editing a page. If you choose the page you want to edit content on you get this nice little view with "editable regions". This hasn't changed since v0.2.0. "Update themes" has been added for super admins. This is primarily for our designer I guess*. See the v0.1.0 version of this page.
This is a page in our Gator Bowl site. Go 'Eers!
* - ok, a short description of how theming works in the system.
1. Designer makes his design.
2. Cuts it out into XHTML & CSS just like normal. Will normally make a home page and back page. He puts this together in a directory in his themes dir. We also have a yaml file for theme-based perms.
3. Drops in a couple of snippets of Ruby code for the nav , the bits to show editable regions (e.g. content_for(:content_1) , yes that easy and no system configuration), can use RoR partials, yada yada yada
4. Runs what we call MockBuilder on his local machine with test data to make sure the templates will work ok.
5. Updates the svn repo with the latest theme.
6. Runs update on the admin side of slate to update slate with the latest version from svn
7. Voila, all done.
This one has been touched on previously. This is the one page in slate that really shows it's evolution and maturity. See the previous link for all the reasons why. Another shot of an old version.
If you want to edit an editable region (that's awkward to say) you click the little icon on the page view and you get this pop-up. A lot of new stuff and a new layout. We now show which version is the published version, link for Textile reference, and improved the "Save" dialogs. The v0.1.0 version.
We grabbed the edge version of RedCloth and I would encourage anyone implementing a CMS to do the same. The auto-linking and the fixes for tags are just great. i wish it was the RedCloth gem.
As great as all the changes have been there's still a lot to be fixed here. Versions aren't working out the way I expected. Users keep clicking save draft every time that make some minor little niggling change or when they want to preview. Makes sense but in our versioning system they're losing access to the last published version and, more importantly, much older versions. I think I'm going to default to 'Save Minor Update' after the first 'Save Draft' and force the user to click out of it.
Preview is also not working the way we planned. I figured people would click the preview pane, go "That looks decent", and get back to the editor pane. Most people really want to go straight back to their page and view the change in context. Makes sense... have no idea how we're going to put in an easy implementation for this. Some users have asked for in-page editing (a la Flickr) but this isn't happening as some editable regions are teeny tiny.
Future updates also include more WYSIWYG-ish buttons for adding Textile formatting and Snippets. Textile is great for typing in content. Most people here are copying and pasting from Word though. Textile is just downright aggravating in this scenario. I'm looking at JS Quicktags to implement that system. Snippets are a little out-of-date with respect to the features they support and they're just so hidden when it comes down to it. Also want to add an upload feature to this editor.
Drupal and Ruby on Rails are two open source technology frameworks that have fueled many Web 2.0 startups.
Двудневен Ruby on Rails семинар за жени - 7-8 март @Telerik Academy.
Събитието се организира на доброволен принцип, с подкрепата на г-жа Гергана Паси, Digital Champion за България.
Двудневен Ruby on Rails семинар за жени - 7-8 март @Telerik Academy.
Събитието се организира на доброволен принцип, с подкрепата на г-жа Гергана Паси, Digital Champion за България.