View allAll Photos Tagged RubyOnRails
Screenshot of what we actually hacked together in about 20 hours or so and presented at Hack Day London. I'm so proud I could crush the sun with my clenched fists.
The list of pages for a site (an earlier iteration). We tried to organize them a little better in terms of being stricter with the layout. Note the new icons that denote an external link that is included in the auto-generated nav as well as a password protected page. We now also have primarily blue icons.
When a super admin logs into slate they get more management options than a regular user. The two big additions to this view with this release is the ability to manage super spaces and the quick find for both sites and users. We have so many sites (312) and users (800+) that it gets difficult to use the pagination or dropdown to find sites/users... especially when we're unsure of spellings.
this is the simple layout when creating a new page (earlier iteration). A lot of the wording on this screen has been updated. "Slug" has been dropped in favor of "permalink." It's also been made a little clearer what the final link will be for a user. This is due to the fact that many users would either a) create pages with really long titles that would by default create long URLs or b) update the page title and forget to update the matching slug. We also made it clearer what a "default page" was now noting it's your home page. We also added "password protection" as one of the options.
Welcome to the geeky side of me. That's what you get when you promise a friend to teach a lesson.
I somehow feel as grey/white as the whole picture is.
And has someone, by any chance, seen that paper plane before? ;)
Almost everything inside our homes (and inside our offices) can be automated. We want to challenge your hacking skills to come up your favorite home or office automation. We'll be hosting with Rocky Moutain Ruby, so expect a huge turn-out and register early. Plus you'll be the first to hack on Chui - the socially intelligent doorbell. The winning team will receive a Chui Doorbell plus dinner and drinks with the founders Shaun Moore, and Nezare Chafni.
Photography by 23rd Studios www.23rdstudios.com Paul Talbot info@23rdstudios.com contact for usage.
Двудневен Ruby on Rails семинар за жени - 7-8 март @Telerik Academy.
Събитието се организира на доброволен принцип, с подкрепата на г-жа Гергана Паси, Digital Champion за България.
Chris has started using lightboxes in WebAdmin 2 for various tasks. This is an example of what happens if you try to delete a page and don't have the appropriate permissions. Lightboxes from what we had seen were originally used with image "pop-ups". Seems like a natural fit though. Next up is snippets. Also look for this when I do the rewrite of SimpleForms. Lightboxes and JotForm-style oh my!
PS - Chris is a genius!
OK, surprisingly enough this screencap is still getting views... if you don't mind could you please leave a note telling me where you heard of this little gem. Thanks!
Двудневен Ruby on Rails семинар за жени - 7-8 март @Telerik Academy.
Събитието се организира на доброволен принцип, с подкрепата на г-жа Гергана Паси, Digital Champion за България.
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.