Broadcast yourself and be heard
PlayMore
Fake is Fake
RapidWeaver blog plugin
I’ve seen the blog page improve by leaps and bounds in my years of developing for RapidWeaver. It’s probably been one of the most actively developed page styles in the RapidWeaver arsenal.
From tagging, to categorizing, archiving and permalinks, RapidWeaver covers many of the basic needs of any would be blogger. And it’s all within the drag-n-drop comfort of our favorite web authoring app.
We can safely say that we wouldn't be as well known as we are if it weren't for blogging technology. It's a free platform to shout our latest news from. Before the days being able to afford professional press releases, our blog was our only means of staying connected to and reaching out to our global audience.
Today, our blog is still as vital as ever, delivering critical information, releases and updates to our readers around the globe.
Oct 2009
Sep 2009
Jun 2008
Mar 2008
Feb 2008
Jan 2008
Sep 2009
Aug 2009
Jul 2009Jun 2009
May 2009
Apr 2009
Mar 2009Feb 2009
Jan 2009
Dec 2008
Nov 2008
Oct 2008Sep 2008
Aug 2008
Jul 2008Jun 2008
May 2008
Apr 2008Mar 2008
Feb 2008
Jan 2008
- Apache
- Apps
- blockquote
- blog feature
- blogging
- classes
- CSS
- dependencies
- design
- Designer
- developers
- doggy
- essay
- facon
- fake
- hardware
- how-to
- It's a doggy
- Loghound
- MAMP
- Mighty Mouse
- multiple
- MySQL
- Perl
- photographer
- PHP
- Plugins
- Pro
- professional
- Quicksilver
- RapidWeaver
- Sey
- seyDoggy
- snippets
- Sony
- testing
- theme
- themes
- trial
- variations
- viEw
- web
- women
- writing
- XAMPP
My most desired feature in RapidWeaver?
06/Oct/09 08:50 AM Filed in: Main Ideas
I get asked this a lot. If you could have any one feature in RapidWeaver, what would it be? I used to have one long standing answer; dependencies in theme development. That was really what I felt RapidWeaver needed for the longest time because there are just some things that could not be overcome with adding more and more css sheets. Things like having sexy graphic layouts, with variable sidebar options, with background color options, with page color options... there is just no way without being able to make RapidWeaver understand if and then at the theme level.
But after years of making RapidWeaver themes and years in web design in general I came to a realization; why strap such complexities on the platform to have to know what theme developers may or may not desire from it when all they would really need to do is add one key component to the RapidWeaver environment as a whole, for the benefit of every end user of the platform. I see no reason why RapidWeaver couldn’t adopt some version of MAMP (or XAMPP) in their rendering environment as opposed to just utilizing Webkit.
Think of the possibilities from an end users standpoint. Someone using RapidWeaver to make a website could have RapidWeaver directly interact with MySQL in a local, controlled setting. They could test PHP scripts without having to go live in the wild. They could build entire sites, front and back, without having to leave the speed and comfort of their own backyard sandbox.
But just think of what this would do to developers? Think of the possibilities we could build into our themes alone. Our template index pages could be php by default with all sorts of crazy possibilities built into them before someone even selects a page style. Like, for example, the long since requested ability to select from multiple index templates that would allow for a variety of HTML element layouts within one theme. With php you wouldn’t need more than one template, just the right cues and triggers to have the desired layout rendered.
For example (and I am just thinking out loud here), in your index template you use the RapidWeaver syntax,
So what is my number one feature request of RapidWeaver? A MAMP environment to play in.
But after years of making RapidWeaver themes and years in web design in general I came to a realization; why strap such complexities on the platform to have to know what theme developers may or may not desire from it when all they would really need to do is add one key component to the RapidWeaver environment as a whole, for the benefit of every end user of the platform. I see no reason why RapidWeaver couldn’t adopt some version of MAMP (or XAMPP) in their rendering environment as opposed to just utilizing Webkit.
Think of the possibilities from an end users standpoint. Someone using RapidWeaver to make a website could have RapidWeaver directly interact with MySQL in a local, controlled setting. They could test PHP scripts without having to go live in the wild. They could build entire sites, front and back, without having to leave the speed and comfort of their own backyard sandbox.
But just think of what this would do to developers? Think of the possibilities we could build into our themes alone. Our template index pages could be php by default with all sorts of crazy possibilities built into them before someone even selects a page style. Like, for example, the long since requested ability to select from multiple index templates that would allow for a variety of HTML element layouts within one theme. With php you wouldn’t need more than one template, just the right cues and triggers to have the desired layout rendered.
For example (and I am just thinking out loud here), in your index template you use the RapidWeaver syntax,
%title%, as a class in you body tag like this: <body class="%title%"> and by simply instructing your users that adding a little cue the the browser title field in the Page Information panel in RapidWeaver, like adding a specific word, they could trigger a whole new layout to appear. A two or three column layout could be called with a simple keyword. The possibilities are endless.So what is my number one feature request of RapidWeaver? A MAMP environment to play in.
|