I have decided to extend the Template Contest deadline to January 1, 2009. Sadly, we received no entries by the October 31 deadline. In order to spark your imagination, here are some suggestions for templates you might make:
If you have started working on one, please finish and submit it. If you haven’t started, here’s your chance!
We had a phenomenal sprint weekend (more like marathon) in Carrboro, NC at Carrboro Creative Coworking thinking, talking, and hacking on Radiant. A big thanks to Brian Russell for donating the space and being so helpful despite being sick! Below are some thoughts and summaries from some of the participants.
Continue Reading…We now have some more tools for your Radiant toolbox:
Andrew vonderLuft has started a bundle for TextMate that helps you write Radius. So if you’re editing your site using TextMate in concert with It’s All Text or something similar, give it a whirl.
Also, today John Muhl completed a Radius language file for Dan Webb’s CodeHighlighter. I’ve added it to my growing collection of highlighters.
Keep up the great work, guys!
Extension developers (and maintaniers) should be aware that Radiant will be moving to Rails 2.1.1 (or perhaps newer) and RSpec 1.1.8 (and perhaps newer).
This means that you may need to update your RSpec syntax in your extensions, so checkout the RSpec site for more: http://rspec.info/documentation/rails/
See David Chelimsky’s post about RSpec 1.1.4 (the version that requires some syntax changes for your specs) for some details: http://blog.davidchelimsky.net/2008/5/27/rspec-1-1-4 Radiant 0.6.9 uses RSpec 1.1.3.
There was a development area for the upgrade but the development there has been pulled into Radiant edge.
We encourage you to test it and provide well-written specs and patches or just plain helpful feedback if you’re not sure how to write the necessary code.
Thanks to a lot of good contributions to Ryan Heneise’s comments extension, Mollom now specifically supports Radiant. Keep up the good work, guys!
Andrea Franz has just released version 0.0.1 of an extension for Radiant that adds support for an iPhone UI:
After some works for iPhone I decided to create an extension for Radiant that adds an iPhone tailored ui for the admin panel. It’s the first version and for now it just allows to edit existing pages and add new page parts.
Here’s a couple of screenshots:
Thank you for making our upcoming community events possible!
Sprout Communication Strategies provides personalized marketing and Web development services with a special focus on health care, technology and veterinary clients. If you are looking for a smart, creative and qualified partner to help you grow your business through marketing and Web development, look no further.
Red Ant is a web design and development firm, based in Sydney Australia. We are 14 Ants. We work on the visual design of web sites, from wireframe through to finished designs. We’re also quite experienced with designing/making web sites for multivariate testing.
We also build sites. Everything from making the HTML templates and Javascript that forms the building blocks of a site, to creating applications that help you manage stuff on your site.
Many of our clients are large consumer brands, so we’ve got quite a bit of experience at making sites that work well and are easy to use. Some of these generate quite a bit of traffic, so we’ve also got some experience in designing/making for high user load.
I mentioned it on the mailing lists the other day, but now it’s official! This is a contest to create new and beautiful templates for Radiant that will be included in the standard distribution. First, the goods:
FIRST PLACE
SECOND PLACE
THIRD PLACE
HONORABLE MENTIONS
Here’s the proposed Radiant shirt design (comments welcome):
/admin/export on your project and save the response as a YAML file (.yml or .yaml extension). You may alternatively use the import_export extension and run rake db:export.seancribbs AT gmail PERIOD com and ws AT johnwlong PERIOD com. Make sure to include the name of your template and your full name so we can give you credit.Judging will be done by the Radiant community for a period of one week after all submissions are received. In addition to overall appeal, criteria may include cleanness of implementation, idiomatic use of Radius, and appropriateness for the audience or site type.
Thanks to Ben Still for sponsoring the prizes for this contest.
The survey for RadiantConf closed this morning, so I thought I’d give an overview of the results. We had 55 respondents in total, with 44 completing the entire survey.
The largest group of respondents were from outside North America, with the majority of those from Europe. Within North America, the Northeast region was the largest.
The top location where people were willing to travel to was the Northeast region, with Southeast and Outside North America tied for second, and Pacific region in third.
The overwhelming majority of respondents preferred a January-March 2009 timeframe, with April-June 2009 being the clear second choice.
The session/activity formats drawing the most enthusiasm were (in order) Tutorials, Open hack sessions/sprints, and Formal presentations. The least favorite were Activities with significant others, Moderated panels, and Social activities.
The most popular topics were Advanced extension development, Site development strategies, and Radiant internals. The least favorite topics were Dev team Q&A, Basics of developing extensions, and Designing and implementing Radius tags.
The preferred conference format was Single-track with an Ad-hoc program, although Multiple-track lost by only 4 votes, and Committee-chosen program by 5.
The majority of respondents were unsure about whether they would submit proposals if a CFP were sent out.
Most people were willing to pay $100-200 to attend, with $51-100 a close second. (in US Dollars)
Of greatest concern to respondents were Travel costs and Hotel costs.
The overwhelming majority preferred to have sponsors to offset registration costs, although many liked getting free stuff or would not be affected by the presence of sponsors.
The question that drew the most free responses was the “topics” question. Here are some of those:
Other general responses about the conference (paraphrased):
I’ve tried to summarize here, but if you require more detail about the responses, please contact me privately or on the mailing list.
Sean Cribbs created an outstanding feature for the latest Radiant (0.6.9). You can now install extensions from the command line:
script/extension install galleryBy default, that script will look at the Radiant Extension Registry to try to find the specified extension. When it is found, the extension will be checked out or downloaded (whichever is appropriate) and it’s migrate and update tasks will be run.
To get some details about what you can do, run:
script/extension helpNot to be confused with this (which I also recommend):
script/extension install helpAnd to find details about an extension you may run:
PC:radiant you$ script/extension info comments Name: comments Description: Adds blog-like comment functionality to Radiant. Author: Ryan Heneise <ryan@artofmission.com> Source code: git://github.com/artofmission/radiant-comments.git Download: Install type: Git
I encourage all extension developers to register at the Radiant Extension Registry to make it even easier for users to find and install your well-written, well-tested and perfect-addition-to-Radiant extensions.
If you haven’t upgraded yet (or even if you have), take a look at John Muhl’s Ray which provides similar functionality through rake tasks to older (and current) versions of Radiant.
One small note for users upgrading from older versions: a minor typo prevents the extension script from being added to your Radiant instance when you run rake radiant:update. To fix this, you could create a new instance of radiant and copy the script over, or freeze to edge to use the command. See this commit for details on the required change.
One of the things that came out of the Radiant BoF Session at RailsConf is that we should have a series of screencasts. I’ve created my first attempt at one and it is available for public consumption here.
The screencast demonstrates installing Radiant from gem, creating a new project, bootstrapping and logging in. It’s a little rough (especially the sound), so comments, advice, and criticism are appreciated.
I’m excited to announce the Radiant CMS Sprint Weekend.
A day to weekend-long hackfest to help finish some features for the 0.7 release of Radiant CMS. The official goals are—refactoring the admin controllers toward REST, implementing a new UI, adding blogging features, improving the extension registry, and writing more documentation.
Saturday, October 25, 2008, 8:00AM-6:00PM (official hours at the venue—unofficially all weekend)
Carrboro Creative Co-working
205 Lloyd St, Suite 101
Carrboro, NC 27510 USA
map | website
Members of the Radiant dev team and community – hopefully you!
Continue Reading…The survey for RadiantConf is now available. If you have some interest in attending, please fill it out. UPDATE: There are three pages to the survey, please fill out all three.
What is RadiantConf?
It’s just in planning stages right now, but it will be a focused conference-like gathering for people interested in using, developing, or learning about Radiant. Your response to the survey will help shape the format of the conference. Don’t miss the chance to voice your opinion! The survey closes on September 13th at 12:00AM EDT.
I am trying to plan a “sprint” weekend for Radiant, and I’d like your feedback.
What’s a sprint weekend? It’s where a group of developers get together to hack out a bunch of code, hopefully speeding up the release cycle. In this initial sprint weekend, we’ll be working on the feature list for Radiant CMS 0.7 “Intaglio”:
Please fill out the survey if you are interested in participating.
As of version 0.6.8, Radiant includes the ability to wrap a block of content with snippets.
Andrew Neil wrote the wrappits extension which adds this ability to Radiant instances of earlier versions. Version 0.6.8 rolled this into the core.
Michael Klett wrote the nested_layouts extension which provides similar functionality but does it with layouts.
Here’s some documentation about how you can use the new features in Snippets, straight from the horse’s mouth. The content below refers to the extension, but it’s all a part of the core now:
Wrappits are an enhanced version of Radiant’s native Snippets. This extension enables you to call a snippet as a double tag:
<r:snippet name="wrapper">
Content between opening and closing tags
</r:snippet>
The "Content between opening and closing tags" can be inserted anywhere within the "wrapper" snippet itself by calling the tag ’<r:yield/>’.
For example, the following could be saved in a Snippet called "rounded-corners":
<div class="top-left rounded">
<div class="top-right rounded">
<div class="bottom-left rounded">
<div class="bottom-right rounded">
<r:yield/>
</div>
</div>
</div>
</div>
The snippet above could then be called, from any Page or Layout, as follows:
<r:snippet name="rounded-corners">
This lorem ipsum has rounded corners, dolor sit amet...
</r:snippet>
In this example, the ’<r:snippet>’ opening tag would correspond to the four opening div tags, and the ’</r:snippet>’ closing tag would correspond to the four closing div tags.
