Radiant documentation - summer reboot

Ruby Apps Radiant CMS
21

David P. wrote:

Silly question – when working with the wiki, how do you create new
pages? Do you just make a link to them and it recognizes a new page has
been made… or something?

It took me a while to figure this out too. Since it is a Rails app
appending “/new” to the URL is the way to do it.

22

Casper F. wrote:

Very nice, Mohit. If everyone can approve of this as starting outline
for Radiant documentation, I suggest you put into a page in the wiki.
Then we can add our names to the sections we would to like write, and
add further sections we think is needed.

I totally missed this post. Sorry for duplicating what you already said!

  • Dave
23

Ben M. wrote:

David P. wrote:

Silly question – when working with the wiki, how do you create new
pages? Do you just make a link to them and it recognizes a new page has
been made… or something?

It took me a while to figure this out too. Since it is a Rails app
appending “/new” to the URL is the way to do it.

Ahh, thanks for the info.

  • Dave
24

Hi David,

I’ve always found building the navigation system in Radiant quite a
hassle, so I have recently added an <r:menu /> to my fork of radiant
(GitHub - RSpace/radiant: Radiant is a no-fluff, open source content management system designed for small teams.
) and submitted a pull request to Sean. I have no idea if it will make
it into Radiant 0.6.8 or even into core at all, but if is does, it
should deprecate most of the r:if_self r:if_ancestor business. It is
very similar to <r:navigation />, but it generates the menu using the
existing page hierarchy in the database, rather than requiring the
developer to hard code it in the tag attributes.

By the way, Mohit, did you create a page in the wiki with your
outline? I can’t seem to find it.

Cheers,
Casper

25

Casper F. wrote:

I’ve always found building the navigation system in Radiant quite a
hassle, so I have recently added an <r:menu /> to my fork of radiant
(GitHub - RSpace/radiant: Radiant is a no-fluff, open source content management system designed for small teams.
) and submitted a pull request to Sean. I have no idea if it will make
it into Radiant 0.6.8 or even into core at all, but if is does, it
should deprecate most of the r:if_self r:if_ancestor business. It is
very similar to <r:navigation />, but it generates the menu using the
existing page hierarchy in the database, rather than requiring the
developer to hard code it in the tag attributes.

That’s a fantastic idea, and I hope it moves into the core. For now,
I’ll still post my navigation how-to, with the hopes we can deprecate it
in the near-future.

  • Dave
26

Mohit S. wrote:

I would like to
initially treat this as a separate ‘handbook’ called ‘Documentation -
Summer Reboot’ rather than into the main handbook. Hopefully, it will
be easy to move pages around later?

I prefer this idea, as long as renaming the main section once we are
done doesn’t break a whole bunch of link slugs.

  • Dave
27

Casper F. wrote:

code it in the tag attributes.

By the way, Mohit, did you create a page in the wiki with your
outline? I can’t seem to find it.

Cheers,
Casper

I’m sorry I’ve been unavailable because we’re participating at a trade
show and it’s been very busy putting things together for that. Should I
create this as a separate page in the wiki, a separate page under the
handbook, or as inidividual items in the handbook? I would like to
initially treat this as a separate ‘handbook’ called ‘Documentation -
Summer Reboot’ rather than into the main handbook. Hopefully, it will
be easy to move pages around later?

Would do you guys think?

Cheers,
Mohit.
6/17/2008 | 11:20 PM.

28

David P. wrote:

  • Dave

Well, it’s done now - let’s hope migrating is easy enough in the future.

http://wiki.radiantcms.org/Summer_Reboot

Cheers,
Mohit.
6/22/2008 | 6:17 PM.