Sitewide Assets

How do people handle site-wide assets like background images? I’d
like to keep everything about the site able to be uploaded/changed.
I’ve got the page_attachments extension, but that seems like it’s only
applicable to individual pages.

I’ve looked at something like the paperclipped, but that seems to
overwrite some of the page attachments functionality.

I’d like to use page_attachments, so what work-arounds are possible
for sitewide stuff, outside of having to deploy them in public/images/*?

Regards,
Josh

There my be an easier way to do this but I use the <r:attachment:url /

tag to discover the actual location of the image. Then if I want,
I can use that information in my css file.

Steven

Sean,

That seems easy enough, I assume then that you are not using the
Scripts N Styles extension then? Maybe that’s the extension that
needs to be written, making page_attachments work with scripts/n/
styles. I know SNS has a more ‘pluggable’ interface now.

Josh

Josh,

Since things like background images are generally applied with CSS, I
like to store my CSS in a Radiant page and then attach the images to
that CSS page.

Sean

Josh,

Although I like what Chris has done, I haven’t had a need for SNS yet.
I may in the near future, as I potentially have more than one Radiant
project on my plate soon.

Sean

Ok, that’s twice in one week (Jim G. just asked for the same thing). I
don’t think this tag belongs in SnS since it depends on Page Attachments
too but a new extension for it might be nice.

Anyone willing to whip up a mini-extension that simply adds the
necessary image tags to the Stylesheet object? I don’t imagine there’d
be much there to do – I’m just not familiar enough with Page
Attachments to know its tags?

Otherwise I’ll look into it in a couple of days.

-Chris

I’ve been thinking I’d try to tackle it, but I’m swamped and I’d love
to see it started.

On Wed, Jul 16, 2008 at 2:59 PM, J Aaron F. [email protected] wrote:

Assets extension though.
We wrote a dead simple assets extension a little while ago. It just lets
you
to upload files directly into radiant’s public directory. We use
page_attachments for almost everything but it has been handy for pushing
out
downloadable files, third party scripts, and other files that we don’t
want
to exist under the page_attachements/dddd/dddd structure. Would this be
of
interest to anyone else?

Cheers,
Stephen

Josh S. [email protected] writes:

How do people handle site-wide assets like background images? I’d
like to keep everything about the site able to be uploaded/changed.
I’ve got the page_attachments extension, but that seems like it’s only
applicable to individual pages.

I started created a generic “Assets” extension for this purpose but
ended up just using the Gallery extension. I’d still prefer a simple
Assets extension though.


J Aaron F. jadetower.com [US] +1 724-964-4515
馮傑仁 cubiclemuses.com [HK] +852 8123-7905

I would love to see it.

Regards,
Josh

Paperclipped is intended to replace page_attachments, I wouldn’t use
both at the same time. I wanted to use something other than
attachment_fu, so I wrote with different functionality than either
gallery or page_attachments. I hope that it offers something that
these do extensions do not. I actually use all three.

There are several ways you could use page_attachments with site wide
images. Sean’s suggestion would be the easiest. Paperclipped uses the
same file structure as paperclipped (as I had started using
attachment_fu), so it is easy to switch if you wish.

You could also add a tab to page_attachments, gaining acces to all the
uploaded images images…

Regards,
Keith

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs