Articles tagged 'new site'
-
New homepage for Rambling Trie
July 28, 2012
This post was originally published in the Rambling Labs Blog on July 28, 2012.
As done with the jQuery Rambling Slider previously on this week, and as I promised on that post as well, the Rambling Trie now has its own homepage on ramblinglabs.com! Here’s the link:
Rambling Trie | A Ruby implementation of the Trie data structure
It features installation and usage steps as well as a contributing page, and includes the badges from various cool GitHub services (more on that later). It also has a brand new logo, inspired on the trie data structure (and other tree data structures) concept.
Go ahead and check it out!
Still pending:
- Examples page for jQuery Rambling Slider
- Examples page for Rambling Trie
- Examples page for Rambling Slider…
-
jQuery Rambling Slider new home page
July 22, 2012
This post was originally published in the Rambling Labs Blog on July 22, 2012.
The jQuery Rambling Slider now has its own dedicated section here on ramblinglabs.com. Here’s the link: jQuery Rambling Slider | A CoffeeScript improved version of the Nivo Slider
It features thus far one download page and one description page with a fully functional slider, included on the site with the rambling-slider-rails gem (see Introducing rambling-slider-rails: Easily include the jQuery Rambling Slider on your rails app and The rambling-slider-rails v0.1.0 has been released!. I will be adding an examples page soon, to present the different themes, image resizing support, flash support and other options added.
Go ahead and check it out!
Also, the Rambling…
-
Writing your blog posts in Markdown with Postmarkdown
February 3, 2012
This post was originally published in the Rambling Labs Blog on February 3, 2012.
Another thing we added to our new site, uploaded back at the end of December, was the ability to write our blog posts in Markdown, which is a text-to-html tool that allows you to write formatted text without actually having to write all the corresponding HTML. Markdown is used for the project wiki pages on GitHub, and can also be used for the project’s readme file.
Most of the time, I don’t like that HTML gets autogenerated for me, since I usually don’t get the results I want. We used to have the site (which was really the blog only) in WordPress, and I never used the autogenerated HTML. In fact, it was quite the opposite: I wrote every blog post in plain…
-
Migrating your blog posts to Markdown with Upmark and Nokogiri
February 3, 2012
This post was originally published in the Rambling Labs Blog on February 3, 2012.
As I said in my last post, for our new site, we changed our blog engine from WordPress to the Postmarkdown gem. At the end of that post, I mentioned that we had to migrate the old posts from WordPress to Markdown.
To do this, we built a ruby script using the Upmark gem and the Nokogiri gem. Nokogiri is used for HTML and XML parsing, among other things, while Upmark is used to generate Markdown from a given HTML.
First, we exported our old blog posts from WordPress to an XML file that looks like this:
<?xml version="1.0" encoding="UTF-8" ?> <!-- This is a WordPress eXtended RSS file generated by WordPress as an export of your site. --> <!-- ... --> <rss
-
Rails 3.1 - Adding custom 404 and 500 error pages
January 5, 2012
This post was originally published in the Rambling Labs Blog on January 5, 2012.
As I said when announcing the Rambling Labs new site, we’ve been learning a lot of stuff while building it.
Something that we didn’t have the chance to implement on our current projects (but that we will be including soon), is adding custom error pages to the site. So far, what we were looking for was two things: a custom 404 error page and a custom generic 500 error page.
For the experience I have now with Rails, I thought this would be a piece of cake. Well, in fact… it would’ve been if we were using Rails 2. But guess what? The error handling behavior in Rails 3 is not what you would expect. Even worse, it’s broken for routing errors!
For what I could…
-
Writing elegant HTML with HAML
January 4, 2012
This post was originally published in the Rambling Labs Blog on January 4, 2012.
Another cool thing that we learned while building the new Rambling Labs site was HAML. It’s a markup language that is based on the premise that ‘Markup should be beautiful’, in their own words.
It’s very easy to install, just add
gem 'haml'
to yourGemfile
and runbundle install
. To use it, replace yourview_name.html.erb
file with aview_name.html.haml
file.Like SASS and CoffeeScript, to achieve the beauty it professes, HAML uses indentation to determine what it should do next. This means, and you guessed it, that it writes beautifully.
Compare this ERb file:
<div id="single_post"> <h2 class="post_title"><%= link_to post.title, post %></h2> <div
-
Generating your site menu with the 'simple-navigation' gem
January 3, 2012
This post was originally published in the Rambling Labs Blog on January 3, 2012.
One of the cool things I learned while building our new site was how to generate your site navigation menu without having to do the highlighting logic yourself.
There’s a great gem out there for this called
simple-navigation
, which you can find on GitHub. It’s easy to set up and use, so you will probably do what you need to do really quick. To install, add it to your rails applicationGemfile
:gem 'simple-navigation'
Then, run
bundle install
. After it’s installed, generate the configuration file for it, which will be theconfig/navigation.rb
, with the following:rails generate navigation_config
Go ahead and open the
config/navigation.rb
file, and add your… -
New look for Rambling Labs!
December 30, 2011
This post was originally published in the Rambling Labs Blog on December 30, 2011.
As you may have noticed, our logo, our favicon, and our site and blog have a new look. We have added a pretty Home page, a cool Contact page and an informative About us page. Also, the blog has moved from it’s original location at the root of the ramblinglabs.com domain to ramblinglabs.com/blog. Every old blog post link and blog tag link has been taken care of and redirects to the new location.
The site is gonna be used as our portfolio site, and will be our first thing to show to our customers. We plan to use it as the center of our developed products and projects. But, hey, don’t worry, we won’t stop blogging!
How the site came to be for the first time…