Re: [Radiant] Reference Assets in

[David Verrier]

Hi Julian,

How did you get started with radiant? Which version are you using?

The best way to get started is to install the radiant gem and use the radiant command to create a new project. This creates a rails 2.x application that runs a user interface for creating pages and managing assets. That usually needs command line access but there is no need to touch the code for getting started. Later, there are many plugins that can add much more functionality.

Initially the version of rails is fixed with the radiant gem version and there is no need to worry about the app directory etc.

You are right about the level of documentation. The github pages seem to have disappeared!

Hope this helps

David V.

On 22 May 2013 16:26, Julian Hurley <jul...@designimperial.com> wrote:

Not a Ruby on Rails beginner, but a pretty major Radiant noob. I've been spent around 4 hours to trying to get a grip on this system, and I'm having difficulty. Not having a go, but as feedback I feel the documentation is really, really patchy.

Anyway, I am making some headway, but I still can't figure out how to reference assets in the source code. If I could edit the slug on image assets that would be incredible, but there's no field edit this, and neither is there a column in the database to reflect it, so that can't be right. How do I reference assets? Where are the images actually stored? 

Also, this is really confusing me. My Radiant application is working perfectly, but where is my app directory? Where are the controllers, views, and models? Very, very confusing!

Anyway, thanks for any help you can give me.

--
 
---
You received this message because you are subscribed to the Google Groups "Radiant CMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to radiantcms+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Sam Whited]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/22/2013 10:26 AM, Julian Hurley wrote:
> Not having a go, but as feedback I feel the documentation is
> really, really patchy.

I couldn't agree more; I haven't been very involved lately (getting
aclimated at a new job), but I've considered sitting down over a
weekend and writing fresh documentation from the ground up. However,
this probably needs to wait until we make some progress on a version
of Radiant that works on Rails 3 and/or 4.

Maybe you'd care to document your setup experience through the eyes of
someone who's never used Radiant before? This could potentially be
very helpful.

—Sam



- --
Sam Whited
pub 4096R/EC2C9934
https://samwhited.com/contact
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJRnPC+AAoJEPs5vPfsLJk0OOAP/iDaCoi5uZcrCaKi842SdU/c
qym3Q7XEsDyOuOdsB7fiR3xMOiWVaq8j1dxwUBPKS3bqzxOoH47N9UdUNMclQhCZ
YOR9XSD4l9BqXrRPoz2LV3K/qLFfAaZftZ6H9fio29q0KKCfE+NM2esOsnU8Bfyt
h/LUxXp3uZN+ub0dvtJ0waPKHqgRIP6SyZXtXaqzG/BdiDByZUFuvq+wsy98Mo8P
QwbvFzNT3AyhoG9N/zMLzn+TZHNDFJa870zS0Fg73NR6PjaQXLW610bJeyCmQyyk
kGPD1e49GDbTxkSWW8+8Bd2dV5/CjhrPe10NuOVbRUTLC7dZxIqqLIAD/vN7mVzd
ogRe11QrU1It/3YD3fCdHON+4JQdKZs0KPrV3ne0Sh4I9lwh3doaKzxCZl+BALiW
GJAJRZcglDD5yeNiVvHpPKcjdedHBacnLiBc3wX/2heDQ3N/EYaX3Z9kD1mPBgt9
4/kmpCMGA+nKgK+rIcM44RCW1LQ549eHiAafdU2O+pUly+U/6BO6HN6HpTylE8A3
6AWJzQtRA/GZBOddmTDvP4HYJXvR6FRt4oIS69+0luG8BEdCUYCk+KX+gU2B46oO
8O9HaS+dWkWKAuMvaLjsz6y/hGZLdlsPsFaN3qvOdqJJIFpFcESetBEGkewK4+GB
lnZTfx6Hxs4+PZtsHzTf
=X9Tw
-----END PGP SIGNATURE-----

[Andrew vonderLuft]

Hi Julian,

Here is some more input on your questions and concerns.

1) On documentation: yes we need more contributors to the project.  If you end up liking Radiant perhaps you could help us out.  :-)  Have you looked here:  https://github.com/radiant/radiant/wiki  ?

2) On using assets:  On each edit pane (pages, snippets, layouts) there is a reference link for "Available Tags"  This pops up a reference, searchable by "Filter Tags" which shows all the available radius tags.  If you filter by "asset" you'll find all the tags used to display assets on pages.  As far as referencing assets in source code, you probably wouldn't do that much, but use the CMS itself and the tagging language.  But to answer your question, the assets are stored in ~/public/assets.  If you want to look at the radiant source code itself, assuming you're using the gem, you can edit `bundle show radiant` from your app root.  

[jul...@designimperial.com]

Yes, I do think better documentation is definitely a really, really, good idea. The ruby CMS war is only between Refinery CMS and Radiant CMS. I've used both, and I feel that Radiant is the better CMS, especially in terms of the interface and the intuitive way you can utilise ruby code in the site's source code.

However, Refinery is much, much easier to set up, and I think that's why it has a larger user-base. If Radiant could refine its installation process, and couple that with some extensive, accessable documentation, I definitely think Radiant could pull ahead.

I'd be happy to document my set up experience, and write extensive documentation regarding the system.

I would be able to rewrite "The Basics" and "Extensions" sections entirely, excluding the "Using Extensions" section, as that's really the domain of the community. Saying that, the "Blogs Extension", "Comments Extension", the "Gallery Extension" and "Database Mailer Extensions" appear to extremely useful, and I would probably be able to document these in the future.

With regards the "How Tos", I'd be more than happy to explain just how to: "Use Radiant as a Blog", "Make a sitemap", "Utilise inline CSS", "Output All Page Parts", "Rest Admin Password", "Change a Page's Publication Date", "Make a Template from an Existing Site", "Migrate SQLite to MySQL" as well as "Setup a SQL Server Database"

I also feel that "Making a Template From An Existing site" and "Migrating from SQLite to MySQL" are so necessary that they should actually be located as an optional section of the installation.

Anyway, those are my thoughts, and I would be genuinely be more than happy to kick-start these sections of the documentation. I can also tell you exactly where the weaknesses in Radiant's installation process lie. All I ask for in return is that you can clarify my questions, which, to be fair, you have been!

All the best,

Julian Hurley

--
 
---
You received this message because you are subscribed to the Google Groups "Radiant CMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to radiantcms+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.