≡ Menu

The new Sentry stack

UPDATE: Here’s a video!

It’s ready!

Although Sentry won’t be “officially” released until next Monday, November 24th, 2014 it is now ready for prime time and I’ve let all our marvelous customers know about it.

Sentry is, to put it simply, a remote control for your website. The Stacks plugin is an indispensable tool for RapidWeaver, and many if not most RapidWeaver users now use it as the default page type.

Sentry is a “container” stack, and any content you add to Sentry can be remotely hidden or displayed on command, or on a schedule that you determine.

This means you can make changes to your site even when you don’t have RapidWeaver, or even a laptop! Yep, Sentry is fully compatible with smartphones and tablets.

We’ve got lots more planned for Sentry, both in future updates, and as a suite of stacks. We hope you enjoy it!



Stack updates galore!

Today we released updates to all of our stacks. These includes some important tweaks and adjustments for upcoming changes to RapidWeaver, so be sure to fire up RW, open a Stacks page and check for updates via the gear icon button in the lower right corner of the Stacks Library.

Depending on the size of your stacks library, it may take a few minutes for updates to appear.

Also, due to how Stacks checks for updates (only once every 24 hours) it may take a day or so for updates to appear, if you’ve recently already checked for updates in the past few hours.

Let us know if you have any question!


Mirage v3.0

Five years is a long time in the internet world – and that’s how long Mirage has been available as a RapidWeaver theme. Really!

The new version of Mirage, released just a couple of weeks ago, is a major upgrade with a ton of new ways to help make your web design life easier.

Instead of having to hand-code complex CSS3 animations, just select the option you want in theme settings and BOOM, smooth page loading animations whenever you want them.

Mirage v3.0 also has much improved responsive support, a sleeker updated design, built-in FontAwesome, Cycle 2 and the fancyBox lightbox plugin – plus a whole lot more than will fit in a blog post!

Take a look at Mirage v3.0, and I hope it helps you create more awesome websites.


Armadillo v1.5 now ready for prime time!

I’ve just released Armadillo v1.5, a huge free update for all Armadillo users. There are lots and lots and lots of new stuff, and we were able to build in many of your most requested features:

  • Unique meta content for each page and post
  • Unique browser title for each page and post (the RW generated one is no longer duplicated)
  • Localized blog dates
  • Security improvements (username and password are sent in separate emails when online setup is complete)
  • New “Blogger” role, just for creating and editing blog posts
  • Fresh new font throughout, and improved Settings layout
  • Lots of bug fixes!

There was even more we wanted to do, so we’ll begin working on the next update, v1.6, here shortly. Some of the things planned for v1.6?

  • Improved support for Joe Workman’s Foundation theme
  • More security improvements, like limiting the number of failed login attempts, etc.
  • And more!

Be sure to get in touch with us know any specific feature requests you have.

We’ve also moved the Armadillo documentation, and hope the new look and feel helps you find what you’re looking for!


Armadillo v1.5 Beta Testing

Just today we’ve started beta testing Armadillo v1.5 which, among many other things, allows you to create unique meta content for individual blog posts. Each page and blog post also will have a unique browser title, to help further improve Armadillo’s SEO performance.

There are a lot more changes under the hood (localized blog date, new dedicated post summary creation, new “blogger” role, etc.), so if you’d like to give the new version a shake down and help us find the last remaining bugs, please get in touch!

If you don’t have Armadillo, you can also purchase it now for 25% off using discount code ArmadilloSummerBeta.

Once you’ve purchased Armadillo, send us an email and let me know you want to join the beta program, and we’ll send you the beta version.


As of today, December 1st, 2013, the seyDesign brand is now being carried on by Jonathan Head (that’s me), the founder and lead developer of NimbleHost.

If you’re a seyDesign customer you may be wondering what’s going to come of seyDesign, and I’d like to ensure you that seyDesign is not going anywhere. Customers are still receiving the same exceptional support. Product updates are still being released. New products are on the way.

In short, we’ve taken great pains to ensure that you won’t be able to tell that anything’s changed at all, and will continue in the tradition of excellence Adam (the original seyDesign founder) has established. Of course, if there are things you’d like to see changed or improved, please do let me know.

If you’re not a seyDesign customer, now is a fantastic time to take a look at the awesome RapidWeaver addons they (well, I guess I should say “we” now) create. You’ll receive the same legendary service at seyDesign that you’ve come to expect from NimbleHost, with top quality themes and stacks perfect for any RapidWeaver project you’ll be working on.

Thanks for your continued support, and I look forward to working with you!




RapidSearch Interruption

It looks like Google has finally pulled the plug on the old web search API that RapidSearch has faithfully used for several years. We are currently working on an update that will switch to the newer Custom Search API.

You may be wondering why we didn’t update RapidSearch sooner – this is because the newer Custom Search API is more restrictive and harder for you, as a RapidWeaver user, to setup and use. In order to do so, you have to first create your own “Custom Search Engine” directly via your Google account (this can’t be done via RapidSearch) and jump through other previously unnecessary hoops. Additionally, ads are now built-in to the experience, and removing them requires that you switch to a paid search account with Google. Our hope was to spare you this pain until it was absolutely necessary, and it seems that time has come.

We’ll be posting more information about the next RapidSearch update here, and via our mailing list (join here). Stay posted, and we’ll get RapidSearch updated to work with the newer API as soon as possible!


RapidWeaver SEO Basics

Many of our customers have been asking about SEO for RapidWeaver, and whether our products work fine for SEO purposes. As such I decided to make a video explaining three basic SEO techniques for RapidWeaver users, to help you understand what makes an impact on your site when you want higher search results rankings.

If you have any questions or comments, be sure to enter them below.

Update: Download the Keynote presentation slides as a PDF:
EnglishGerman* – French (courtesy of Philippe)

*This translation is via Google Translate. If you’re a native speaker and it sounds weird, that’s why! ;-)



myMenu v3.0

We’re very close to releasing a huge update to the very popular myMenu stack, adding the two most requested features we’ve gotten for this stack to help make your web design life easier:

  1. Responsive layout support
  2. Custom menu items with their own sub-pages

But rather than explain all this in blog post, why don’t you see it in action? ;-)



Keep an eye on your inbox, as we’ll be sending out an email when the update goes live. If you’re not already a NimbleHost member, you can join our mailing list on this page.

Please leave your comments and questions below!


I’ve got cruftless links. Now what?

This is the (long awaited) follow-up article to my post about how cruftless links are better for SEO. If you haven’t read that post be sure to do so first, as this article will make more sense at that point.

So now that we’ve established how awesome cruftless links are, many of you have already switched over to them; and the next question I always get is how to make sure the old links are redirected to the new. This is something we need to address for a number of reasons:

  • Chances are that search engines have your old links saved to their index, and this allows us to make sure they see and index the new ones. It’s possible your ranking on SERPs (search engine results page) could drop if this isn’t done.
  • It makes the transition painless for your website visitors. Nobody wants to visit your site and see a 404 Not Found error.

For most people the best way to tackle this problem is by using a .htaccess file and specifying something called “rewrite rules”. If your web hosting uses Windows and IIS, then you can do (essentially) the same thing with what’s called a web.config file, but I won’t be covering that in this article.

Before we get started you’ll need to make sure that your hosting provider meets the requirements for what we’re about to do. I have a list of compatible hosting companies that we know support this, but the list isn’t exhaustive. Even if your hosting company isn’t listed that doesn’t mean this won’t work, only that you’ll need to confirm the following:

  • Your hosting uses the Apache web server (most companies do)
  • The mod_rewrite module for Apache is installed and enabled (again, most companies already do this)

Depending on the configuration your hosting company uses, you may need to enable the .htaccess file in your hosting control center. Also, be sure that you have FTP access to your hosting account, as you’ll need to edit/upload the .htaccess file directly to your hosting account, in the same folder where your homepage is located. If you already have a .htaccess file in that location, don’t delete or replace it. Instead, open it in a good text editor, and add your code to the end of that file. With all that said, let’s get started.

Let’s say your old link looked like this:


And you’ve updated that to a shiny, new cruftless link, like so:


Obviously the goal is to make sure that anyone who tries to visit the old link is redirected to the new link. We can do this in the .htaccess file using this bit of code:

RewriteEngine On
Redirect 301 /photos.html http://bigfootsupersite.com/photos

Looks fairly simple, and I’m guessing you can read this and make out what is going on. Let’s walk through the code line by line.

The RewriteEngine On line does exactly what you might expect. It turns on the engine you’ll be using to redirect visitors to the page you want them to see. We need to make sure this is turned on first, before starting our redirect code.

The next line is where the magic happens. The Redirect command is quite simple – you’re telling the server where your website is located that you want to redirect something. But we also need to provide some additional information – more specifically, what type of redirect this is, the old page that people will be trying to access, and the new page where you want them to be redirected.

The 301 number is specific type of redirect, called a “permanent” redirect. This tells web browsers and the search engines crawling your site the old page has been permanently replaced with the new one. By using this “permanent” redirect, search engines will automatically update their indexes to use the new cruftless link.

After that we have the /photos.html portion. This is the old page that people (and search engines) will be trying to access.

Finally we have the http://bigfootsupersite.com/photos portion. You’ll recognize this as our new cruftless link, and it’s where people who try to access the old page will be redirected.

If you have more than one page to redirect, you can add as many Redirect lines as you need. Here is an extended example, based on the same code above:

RewriteEngine On
Redirect 301 /photos.html http://bigfootsupersite.com/photos
Redirect 301 /reported_sitings.html http://bigfootsupersite.com/sitings
Redirect 301 /contact/contact.php http://bigfootsupersite.com/contact

Note that we only need to use the RewriteEngine On line once. The last line also shows how to target sub-pages in your site. As a reminder, the .htaccess file should be placed in the same location as your homepage. If there’s already a .htaccess in that location, just open the file and add your code to the end.

Of course, be sure to test our your redirects when your done, to make sure they are working correctly.

EDIT: As requested in the comments, here is how to redirect any 404 Not Found errors to the homepage. This will work anytime a visitor tries to access a page or file that can’t be found on your website, and can be done in the .htaccess file like so:

ErrorDocument 404 http://bigfootsupersite.com

This is a good fallback method if you don’t remember all the old URLs and want to make sure visitors can still navigate your site even if they try to access a page that doesn’t exists anymore.

Before wrapping up this article I want to make sure we cover the importance of a good text editor. You don’t want to be using a program like TextEdit or Notepad, as they oftentimes will add extra data to the file, or impose a certain file extension (like, .txt, .rtf, etc.). Instead, be sure you are using a text editor designed to work with code. This is easy to do, and free! For Mac users there is the free TextWrangler from Bare Bones Software. For Windows users I’d suggest the free Notepad++ (not to be confused with the regular Notepad app included with Windows by default).

Another note specifically for Mac users. By default Mac OS X hides files that start with a period, such as .htaccess files. As such I recommend that you create the file on your hosting account directly. You can then right-click on the .htaccess file in your FTP program, and from the contextual menu select to edit the file in your text editor of choice. The nice thing about this approach is that your FTP client should automatically upload the file when you save your changes. Easy!

Hope this helps you make the transition to cruftless links. Make sure to leave your feedback in the comments below.