RE: [Radiant] New Radiant powered site
Very nice! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marshal Linfoot Sent: Wednesday, April 16, 2008 9:53 AM To: Radiant@radiantcms.org Subject: [Radiant] New Radiant powered site Hi all. I wanted to say a big thank you to everyone involved in the Radiant development and also to everyone contributing tips/suggestions on the mailing list. I'm using Radiant for a fairly simple website and finding it very easy to use and very flexible. The website is http://www.octopusgardenyoga.com and it uses a few third-party extensions: gallery, reorder, scheduler, and shards. A special thanks to the people who contributed these great additions. Again, thanks to all and if you have any questions about how our site was constructed, please ask. -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant and Flex
Say, Is anyone using Radiant as a back-end for Flex/Flash applications? I'd like to try this, but was hoping to get some pointers. Thanks, Marcus Marcus Blankenship 541-882-3451 x 2558 [EMAIL PROTECTED] Lorem ipsum dolor sit amet, consectetur... ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] Radiant and Flex
First, let me acknowledge that Sean answered a very similar question to this earlier this year, so I'm sorry for the repeat post. I cannot find anyone on the net who's done this, so I may be barking up a stump instead of a tree. Let me see if I can explain why I was considering it, and someone can tell me I'm crazy. I currently drive my Flex content from the PHP CMS Drupal, which works fine but feels like overkill for what I need. My primary motivation is quickly getting an HTML site behind my Flex application (for SEO purposes). Secondary, having Drupal/Radiant on the back-end gives the site admins a way to easily update content without me having to re-code anything. Drupal has an AMFPHP gateway module, which I can take advantage of in Flex. I think the way I could accomplish something similar with Radiant would be to use data in XML (rss?). Does this sound right? Does rails have any AMF libraries that could be integrated with Radiant? Thanks in advance, Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Van Dyk Sent: Thursday, October 02, 2008 12:14 PM To: radiant@radiantcms.org Subject: Re: [Radiant] Radiant and Flex On Thu, Oct 2, 2008 at 11:45 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Say, Is anyone using Radiant as a back-end for Flex/Flash applications? I'd like to try this, but was hoping to get some pointers. You would probably want to write an extension that interfaces with the flex application. Not sure what the benefit of using Radiant would be though. Joe ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] Radiant and RubyAmf
Thanks for all the info. I believe when you use RubyAMF, you basically expose all your objects as AMF using scaffolding. I'll play with it and see where I get. Are you pulling Radiant content into any Flash apps? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nate Turnage Sent: Wednesday, October 08, 2008 10:32 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Radiant and RubyAmf On Wed, Oct 8, 2008 at 12:08 PM, Marcus Blankenship [EMAIL PROTECTED]wrote: Thanks, Nate. So, to clarify because I'm dense: 1. I need to build an extension 2. The archives/docs should show me how. Will I need to learn git to do this? They should. You only really need to know git if you are manging your code in that system. The only thing you really need to know about git for installing extensions is that to add an extension to your project from git you use the clone url from the project like so: git clone http://address/of/project/name_of_extensionvendor/extensions/name_of_ext ension . That will clone the git repo into your extension folder. All of the rest of the info on extensions is on the radiant website. Again, specific questions will usually get answered here. As you may suspect, my end goal is to get either the content alone or the stylized content (not sure which) from Radiant and display it in Flex via AMF. I intend to do my own styling in Flex, but I would like any HTML markup that the user may have entered. Does this seem feasible? It sounds like you may want to expose your pages from radiant as xml (use the page type XML). Then you can use whatever you want on the front end to read and style that file accordingly. I don't know how that figures into RubyAmf and what it does, though. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] Radiant T-Shirt design - Please give input!
How do we order? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Cribbs Sent: Thursday, October 09, 2008 1:07 PM To: radiant@radiantcms.org Subject: Re: [Radiant] Radiant T-Shirt design - Please give input! Okay, thanks for all of your responses. I'm going to order today, going with the left-front pocket area, logo with the text, nothing on the back. The first round of shirts will be black, but we may have other options (including other designs) if the demand is enough. Cheers, Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors?
Everyone can get out their shotgun for what I'm about to say, but... BigMedium CMS (www.globalmoxie.com) is an excellent example of a user-friendly CMS that non-techies can use. Maybe that could be our model. If you haven't played with it, you should, as Josh has done a great job of abstracting the nerdy parts from users. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam van den Hoven Sent: Tuesday, November 18, 2008 10:01 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I'd like to see this too. I use it for exactly this purpose, to give non-technical people the ability to manage a simple website using a CMS. To be honest, I think that the mostly technical person doesn't really need an OS CMS, they can either hand code the HTML just as easily (maybe run some scripts to generate naviation) and upload the files via ftp/svn or write their own CMS. Its precisely when we have more complicated needs (of which multiple, non-technical users is a likely one) that Radiant becomes most useful. I have some thoughts on this: 1) What would be awesome would be a WYSIWIG editor plugin that is an EXTENSIBLE HTML/XML editor. This would allow one to create GUI elements for all of the common radius tags (override creating links, for example, putting an asset browser into there, etc) and have it create the necessary markup. Maybe a markup WYSIWYG editor will allow this too but I don't know of any 2) Normally when someone wants a custom template that captures something specific (a news article or a product) really its just a way to more seamlessly (and realiably) enforce content structure (here is you headline, here is your kicker, a product image goes in this box) but really all we want to do is generate structured markup for various parts. It would be wonderful if one could create page templates that imposed some sort of structure but behind the scenes simply added a page to the database with a number of parts with predefined markup. (I'm not sure if this is like the templates extension Sean released.. Haven't had a chance to look at it). Making it part of the pages structure keeps it clear where it appears. On the other hand, you can tell your client that if they really want all that they're looking at a system like Teamsite from Interwoven which would probably cost them in the range of a half million plus 10% per year (but don't forget to put your 4% markup on that)... Adam On 18-Nov-08, at 9:44 AM, Casper Fabricius wrote: Hi everyone, I've used Radiant for more than 10 web sites during the past 1,5 years, and I really like it. Definitely the best CMS for Rails. However, I have a client whose content editor is very frustrated with the system. She can only just tolerate using Markup, and she refuses to write any kind of HTML - Radius tags falls into this category from her point of view. According to her, a proper CMS would hide all this technical stuff and provide custom forms for all types of content. I know what the core team might answer: Radiant CMS was not built for this woman. It was built for small sites and content editors with a bit of technical insight. But Radiant is still the most user- friendly CMS that exists for Rails, and I don't really feel like coding PHP just get a more advanced UI, which will suck anyway. So my question is: How do the rest of you handle this? How do you hide away technical stuff such as snippets, tags and css classes? Do you: - Use any of the WYSIWYG filters? (I've done this a few times, it has its own problems) - Build very specific custom layouts for all variants for pages? - Use a generic templating interface such as radiant-templates- extension to wrap everything up? - Write custom extensions to wrap all kinds of elements nicely in forms? (such as newsletters, spots, list of various items, etc.) Can Radiant be palatable for content editors such as my client, or is it simply the wrong choice in this case? Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors?
Another thought, crazy as it might be, would be to create a FLEX component that represents a content editor. We do this on some of our flex apps, and it works well. Here's an example: http://cfsilence.com/blog/tips/rte/bin/richTextEditor.cfm This might allow for more control than JS based editors give, I'm not sure. Just another thought, from a FLEX nerd. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casper Fabricius Sent: Wednesday, November 19, 2008 10:21 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: Casper Fabricius wrote: However, I have a client whose content editor is very frustrated with the system. She can only just tolerate using Markup, and she refuses to write any kind of HTML - Radius tags falls into this category from her point of view. According to her, a proper CMS would hide all this technical stuff and provide custom forms for all types of content. Casper, my solution would be to find a slightly more technical client :P No, I'm joking (of course!) Here's what I would recommend: 1. First, factor out as far as possible so that whatever is not page specific is in snippets. 2. If all she needs is a few styles of pages, I would create different page types or layouts. 3. Then tell her that the different parts that she wants need to go into different page parts. It would be cool if you could modify the Add Child behavior to allow you to
RE: [Radiant] Can Radiant be really easy to use fornon-technicalcontent editors?
Sorry, then. Yes, the Flex language/compiler is open source, and that app was as well. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Gehring Sent: Wednesday, November 19, 2008 10:39 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use fornon-technicalcontent editors? Off topic, possibly... But is that FLEX app open source? Andrew On Wed, Nov 19, 2008 at 11:28 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Another thought, crazy as it might be, would be to create a FLEX component that represents a content editor. We do this on some of our flex apps, and it works well. Here's an example: http://cfsilence.com/blog/tips/rte/bin/richTextEditor.cfm This might allow for more control than JS based editors give, I'm not sure. Just another thought, from a FLEX nerd. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casper Fabricius Sent: Wednesday, November 19, 2008 10:21 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: Casper Fabricius wrote: However, I have a client whose content editor is very frustrated with the system. She can only just tolerate using Markup, and she refuses to write any kind of HTML - Radius tags falls into this category from her point of view. According to her, a proper CMS would hide all this technical stuff and provide custom forms
RE: [Radiant] Can Radiant be really easy to usefornon-technicalcontent editors?
Oh, sorry. ;-) This is the original page, and has a source link. (http://weblogs.macromedia.com/mc/archives/disclosableRTE.zip) If you like that sort of thing, here's a few more flex resources. Forgive if this if off topic. Adobe Flex downloads page: http://www.adobe.com/products/flex/flexdownloads/ Nice, free actionscript / Flex IDE: http://www.flashdevelop.org/community/ I you want any help getting it compiled/changed/working, let me know. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Gehring Sent: Wednesday, November 19, 2008 10:45 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to usefornon-technicalcontent editors? I didn't mean your post was off topic, I meant mine might be :-) What/where is the source to the app? Thanks, Andrew On Wed, Nov 19, 2008 at 11:41 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Sorry, then. Yes, the Flex language/compiler is open source, and that app was as well. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Gehring Sent: Wednesday, November 19, 2008 10:39 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use fornon-technicalcontent editors? Off topic, possibly... But is that FLEX app open source? Andrew On Wed, Nov 19, 2008 at 11:28 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Another thought, crazy as it might be, would be to create a FLEX component that represents a content editor. We do this on some of our flex apps, and it works well. Here's an example: http://cfsilence.com/blog/tips/rte/bin/richTextEditor.cfm This might allow for more control than JS based editors give, I'm not sure. Just another thought, from a FLEX nerd. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casper Fabricius Sent: Wednesday, November 19, 2008 10:21 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're
RE: [Radiant] If you love radiant but need ecommerce what's the bestsolution
Okay, my vote for best eCommerce solution, anywhere, is Magento. (www.magentocommerce.com) I love it very much! ;-) Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Rönnqvist Sent: Wednesday, November 26, 2008 12:28 PM To: radiant@radiantcms.org Subject: Re: [Radiant] If you love radiant but need ecommerce what's the bestsolution Hi! I've found the shopping module Übercart for Drupal really good. Of course Drupal is PHP-based and all... but really flexible and has a lot of other modules, so very seldom I find myself coding PHP when using Drupal anyways. Generally speaking I use Drupal for more advanced sites, with lots of features, although pretty standard ones (so that you can find ready made modules for them)... while as Radiant CMS again is more appropriate for simpler sites when you want things working your way without much hassle and configuration. http://www.ubercart.org/ cheers, Simon PS. There's also the Drupal E-commerce module, but I find Übercart more ready out of the box.. and its community seems more active too. On Nov 26, 2008, at 22:17 , Steven Southard wrote: Radiant is such a nice platform to develop on that it really pains me to choose another CMS for an upcoming website. It's mainly a brochure site but they also sell about 50 products. They currently have an outdated CMS and a yahoo shopping cart. They want to move forward with an integrated approach. I've been trying out Substruct which has both of these features. The Cart is great but the CMS just fall short of what I've gotten accustom to. Mainly, there's no control of the layout or CSS from the back-end. It might be possible to fix that but I'm not sure how much work it would be. I've also looked at Spree. It looks okay for a cart but doesn't seem to have any other CMS type functions. Maybe it would work well side by side with Radiant or as sub domain but I don't see any way it could be integrated. What are some other approach people have taken to give this type of client what they need? Steven http://www.stevensouthard.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] If you love radiant but need ecommerce what's the bestsolution
Steven, Just checked out your home page. You do nice work! Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Southard Sent: Wednesday, November 26, 2008 12:18 PM To: radiant@radiantcms.org Subject: [Radiant] If you love radiant but need ecommerce what's the bestsolution Radiant is such a nice platform to develop on that it really pains me to choose another CMS for an upcoming website. It's mainly a brochure site but they also sell about 50 products. They currently have an outdated CMS and a yahoo shopping cart. They want to move forward with an integrated approach. I've been trying out Substruct which has both of these features. The Cart is great but the CMS just fall short of what I've gotten accustom to. Mainly, there's no control of the layout or CSS from the back-end. It might be possible to fix that but I'm not sure how much work it would be. I've also looked at Spree. It looks okay for a cart but doesn't seem to have any other CMS type functions. Maybe it would work well side by side with Radiant or as sub domain but I don't see any way it could be integrated. What are some other approach people have taken to give this type of client what they need? Steven http://www.stevensouthard.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] Available for contracts
Sean, what is your contact info? -Original Message- From: radiant-boun...@radiantcms.org [mailto:radiant-boun...@radiantcms.org] On Behalf Of Sean Cribbs Sent: Wednesday, April 01, 2009 4:02 PM To: radiant@radiantcms.org; radiantcms-...@googlegroups.com Subject: [Radiant] Available for contracts This is just a notice that I am available for consulting and development on Radiant, Rails, Ruby and Erlang projects, up to about 25 hours a week. I have been doing Ruby on Rails for over 3 years and Radiant for nearly that long. Please contact me privately if you are interested. Cheers, Sean Cribbs P.S. Apologies to those who receive this more than once. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
