Is there some way with Radiant to automatically generate an index of the
headings at the top of the page, as we see on so many sites?
I realise that I can have a
r:children:each
* r:link /
r:content //p
/r:children:each
that would pull the sub-pages together and give the appearance of one
I think he means anchors! That's a good question - I have no idea how
to generate anchors automatically in a Radiant page. I don't think
there's a direct way :(
Cheers,
Mohit.
3/16/2009 | 11:50 PM.
Sean Cribbs wrote:
I don't understand. Do you mean a Table of Contents?
Sean
Anton
Sean Cribbs said the following on 03/16/2009 11:39 AM:
I don't understand. Do you mean a Table of Contents?
Yes, but more than that. I realise my subject isn't quite right but I
really don't know how to explain it in one line.
Here's the business use-model:
While many sites that list
Mohit Sindhwani said the following on 03/16/2009 11:50 AM:
I think he means anchors! That's a good question - I have no idea how
to generate anchors automatically in a Radiant page. I don't think
there's a direct way :(
Half way there! Not just the anchors but some 'standard' thing so
Anton Aylward wrote:
Sean Cribbs said the following on 03/16/2009 11:39 AM:
I don't understand. Do you mean a Table of Contents?
Yes, but more than that. I realise my subject isn't quite right but I
really don't know how to explain it in one line.
Here's the business use-model:
Announcing the Radiant Member Extension.
* Restricts access to Radiant pages under a certain node, requiring
member login.
* Members can be managed from Radiant Admin. There is *NO* member
self-registration.
* Reset and email member’s password from Admin interface;
* Bulk import members from
On 3/16/09 6:13 PM, Istvan Hoka wrote:
Announcing the Radiant Member Extension.
* Restricts access to Radiant pages under a certain node, requiring
member login.
* Members can be managed from Radiant Admin. There is *NO* member
self-registration.
* Reset and email member’s password from
Mohit Sindhwani wrote:
You could try this:
* Create each bio page separately as you suggested
* Create a special page part called 'anchor' in the bio page
You could then write a special tag that creates a link to that anchor
using r:children:each
and a special tag similar to r:content called
Hi everyone!
We have made some changes to Paperclipped we thought you might like:
* r:assets:each enhanced with limit, offset, order, by, extension
filtering;
* r:if_assets and r:unless_assets tags for conditional rendering;
* r:assets:width and r:assets:height via imagesize gem;
* better
Hey guys,
I am new to Radiant, in fact I haven't done anything with it yet. But i've
been struggling with Drupal and ExpressionEngine and want to move toward
something that uses ruby and would really like to be able to pitch radiant
to my boss or my clients. One of the main questions i have about
Istvan Hoka wrote:
Hi everyone!
We have made some changes to Paperclipped we thought you might like:
* r:assets:each enhanced with limit, offset, order, by, extension
filtering;
* r:if_assets and r:unless_assets tags for conditional rendering;
* r:assets:width and r:assets:height via
Youssef,
This is the perennial question. I should make a wiki page for it!
Although there are a million variations on them, the three main
strategies are thus -
1) Build customizations/other apps as Radiant extensions (most popular)
2) Keep Radiant and your other app in parallel, as
You could try this:
* Create each bio page separately as you suggested
I agree. This is a good way to go.
* Create a special page part called 'anchor' in the bio page
You could then write a special tag that creates a link to that
anchor using r:children:each
and a special tag similar to
On Mar 16, 2009, at 3:49 PM, Sean Cribbs wrote:
Youssef,
This is the perennial question. I should make a wiki page for it!
Although there are a million variations on them, the three main
strategies are thus -
1) Build customizations/other apps as Radiant extensions (most
popular)
2)
I'm writing an extension and want to run autotest against my rspec
tests. Is there anything I have to configure to get it to work? When I
run it with -v, I get No tests matched ... for all of the files in
my tree. I'm starting autotest from my extension directory.
Aloha a hui hou,
Ken
--
Nice feature, better thant the litte if_attachment hack i added for
my projects ;)
but i got one problme, wich is not quite related to your improcements,
but maybe someone has a clue:
when i run
rake radiant:extensions:migrate:paperclipped
i get an error stating this:
== 20090316132151
Andrew Neil wrote:
You could try this:
* Create each bio page separately as you suggested
I agree. This is a good way to go.
* Create a special page part called 'anchor' in the bio page
You could then write a special tag that creates a link to that anchor
using r:children:each
and a
michael starke wrote:
Nice feature, better thant the litte if_attachment hack i added for
my projects ;)
but i got one problme, wich is not quite related to your improcements,
but maybe someone has a clue:
when i run
rake radiant:extensions:migrate:paperclipped
Are you sure you didn't
Mohit Sindhwani wrote:
Andrew Neil wrote:
You could try this:
* Create each bio page separately as you suggested
I agree. This is a good way to go.
* Create a special page part called 'anchor' in the bio page
You could then write a special tag that creates a link to that anchor
Hey all,
Trying to get the image title to render as the link title attribute but
title=r:title / is rendering out as title=lt;r:title /gt; in the
following snippet:
notextile
r:attachment:each limit=2 offset=1 order=asc
div class=galleryThumb
r:attachment:link rel=facebox-cap title=r:title
Christian Vetter wrote:
That's good! I always get confused whether #r:slug / works! But I
guess it does.
You can put radius tags wherever you want, except within other radius tags;
that means you can set attributes to radius tags and have their output as the
attriute's value in your
21 matches
Mail list logo
