[pmwiki-users] Revisit the thread - How to create Directive for Titles

Rene Visco rvisco at csdr-cde.ca.gov
Tue Oct 11 14:19:16 CDT 2005


Hi,

Working with a few curriculum specialists in my department, I came across a
very repetitive tasks related to Page Title.

Since we already have documents in our servers such as state educational
standards, etc., we will create wiki pages to match the documents in our
current servers and linking to various documents.

Basically, we're creating wiki pages to make a clean "outline" of our
documents with various links, as opposed to "creating" new blank pages.

Let me give you an example of a page that we developed for Applied
Academics:

!!! Units
*[[AAMSUnitsY1S1 | Year 1 - 1st Semester]]
*[[AAMSUnitsY1S2 | Year 1 - 2nd Semester]]
*[[AAMSUnitsY2S1 | Year 2 - 1st Semester]]
*[[AAMSUnitsY2S2 | Year 2 - 2nd Semester]]
!!! Content Standards
*[[AAMSStandardsY1S1 | Year 1 - 1st Semester]]
*[[AAMSStandardsY1S2 | Year 1 - 2nd Semester]]
*[[AAMSStandardsY2S1 | Year 2 ­ 1st Semester]]
*[[AAMSStandardsY2S2 | Year 2 ­ 2nd Semester]]
!!! [[Standards Checklists Order Form]]
!!! Standards Checklists
*[[AAMSStandardsChecklistsY1S1 | Year 1 ­ 1st Semester]]
*[[AAMSStandardsChecklistsY1S2 | Year 1 ­ 2nd Semester]]
*[[AAMSStandardsChecklistsY2S1 | Year 2 ­ 1st Semester]]
*[[AAMSStandardsChecklistsY2S2 | Year 2 ­ 2nd Semester]]

As you can imagine, we HAVE to use page title directive to properly title
each wiki page.  

It's a drag to instruct and explain to them that we need to use (:title:) on
the top of the page to title it properly.

So, I think it's best to incorporate a form field similar to "summary" and
"author" form field and put it on the top so users have the option to title
it (only for the invoice users and it's more friendly).  Suppose if we did
not fill in the title's form field, it will be the title of the "wiki word".

I would vouch for "title" form field rather than using GUI buttons for page
title directives.

Rene V.  




>On Fri, Oct 07, 2005 at 09:06:58PM +0200, Dominique Faure wrote:
> This was not so hard: in fact we only needed something whing could be
> rendered *at the end* as a '$':
> 
> $GUIButtons['h1'] = array(400,
>                          '(:title TypePageTitle:)\\n!{$Titlespaced} ',
>                          '\\n', '$[Page Title]',
>                          '$GUIButtonDirUrlFmt/h2.gif"$[Page Title]"');

I think you guys mean this:

$GUIButtons['h1'] = array(400,
                         '(:title ',
                         ':)\\n!{$Title}',
                         '$[Page Title]',
                         '$GUIButtonDirUrlFmt/h2.gif"$[Page Title]"');

so that whatever text is highlighted gets used as the title. Also, using
{$Titlespaced} doesn't make much sense (to me) if you're typing in the title
anyway, so I've replaced it with {$Title}.

Though, this seems of limited usefulness as a GUI button. It's a button that
you'll use at most once per page whereas the other GUI buttons can be used
over and over again throughout the document.

It seems like it would be best to just have a specialized markup (as the
subject of this thread says) that gets transformed into the appropriate
markup on page save. I seem to recall that PmWiki has this ability, but I
don't remember how to trigger it off hand.





More information about the pmwiki-users mailing list