hi guys, some of the pages on the wiki are getting quite large ( eg. http://wiki.centos.org/HowTos/BuildingKernelModules ), and its not easy to work out what all might be included in the page, without actually going through most of it ( were going to loose context in this case ) What would be a better option ? to split the pages up into more manageable chunks or to just create an index on the top of the page that points at each section of the page ? - KB -- Karanbir Singh : http://www.karan.org/ : 2522219@icq
On Tue, Jul 03, 2007 at 11:49:59AM +0100, Karanbir Singh enlightened us: > some of the pages on the wiki are getting quite large ( eg. > http://wiki.centos.org/HowTos/BuildingKernelModules ), and its not easy to > work out what all might be included in the page, without actually going > through most of it ( were going to loose context in this case ) > > What would be a better option ? to split the pages up into more manageable > chunks or to just create an index on the top of the page that points at > each section of the page ? > I would vote for the latter. There may already even be functionality to do that automatically with a macro. If not, we'll just make Daniel write it :-) Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Matt Hyclak wrote: >> What would be a better option ? to split the pages up into more manageable >> chunks or to just create an index on the top of the page that points at >> each section of the page ? > I would vote for the latter. There may already even be functionality to do > that automatically with a macro. If not, we'll just make Daniel write it :-) Yeah, perhaps adding an index is going to be the easiest, and it wont create a massive number of related pages. I know twiki has something like this, no idea if Moin does as well. - KB -- Karanbir Singh : http://www.karan.org/ : 2522219@icq
On Tue, 2007-07-03 at 11:49 +0100, Karanbir Singh wrote: > hi guys, > > some of the pages on the wiki are getting quite large ( eg. > http://wiki.centos.org/HowTos/BuildingKernelModules ), and its not easy to work > out what all might be included in the page, without actually going through most > of it ( were going to loose context in this case ) > > What would be a better option ? to split the pages up into more manageable > chunks or to just create an index on the top of the page that points at each > section of the page ? Maybe we should add the [[TableOfContents]] macro on top of long pages? -- Daniel
Daniel de Kok wrote: > On Tue, 2007-07-03 at 11:49 +0100, Karanbir Singh wrote: > > some of the pages on the wiki are getting quite large ( eg. > > http://wiki.centos.org/HowTos/BuildingKernelModules ), and its not easy to work > > out what all might be included in the page, without actually going through most > > of it ( were going to loose context in this case ) > > > > What would be a better option ? to split the pages up into more manageable > > chunks or to just create an index on the top of the page that points at each > > section of the page ? > > Maybe we should add the [[TableOfContents]] macro on top of long pages? Yes, IMHO a good idea. I already did that for pages which are for more than one version of CentOS, see <http://wiki.centos.org/Repositories/RPMForge> for example. Cheers, Ralph -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.centos.org/pipermail/centos-docs/attachments/20070703/99d7893d/a...
On 7/3/07, Ralph Angenendt <ra+centos@br-online.de> wrote: > Daniel de Kok wrote: > > On Tue, 2007-07-03 at 11:49 +0100, Karanbir Singh wrote: > > > some of the pages on the wiki are getting quite large ( eg. > > > http://wiki.centos.org/HowTos/BuildingKernelModules ), and its not easy to work > > > out what all might be included in the page, without actually going through most > > > of it ( were going to loose context in this case ) > > > > > > What would be a better option ? to split the pages up into more manageable > > > chunks or to just create an index on the top of the page that points at each > > > section of the page ? > > > > Maybe we should add the [[TableOfContents]] macro on top of long pages? > > Yes, IMHO a good idea. I already did that for pages which are for more > than one version of CentOS, see > <http://wiki.centos.org/Repositories/RPMForge> for example. > > Cheers, > > Ralph I see. The key is to use = == === to index items on the page? Akemi
Akemi Yagi wrote: > On 7/3/07, Ralph Angenendt <ra+centos@br-online.de> wrote: >> Yes, IMHO a good idea. I already did that for pages which are for more >> than one version of CentOS, see >> <http://wiki.centos.org/Repositories/RPMForge> for example. > > I see. The key is to use = == === to index items on the page? = == === are different levels of headings - like h1 h2 h3 and so on in HTML. [[TableOfcontents]] Then takes those headings and expands them into a content table (which appears on the page at the point you add the macro). Keep in mind: Even if you insert [[TableOfContents]] *after* some headings, those will be taken into account. So normally you want to put the macro near to the top of the page. Cheers, Ralph -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.centos.org/pipermail/centos-docs/attachments/20070703/9272cf47/a...
On 7/3/07, Ralph Angenendt <ra+centos@br-online.de> wrote: > Akemi Yagi wrote: > > On 7/3/07, Ralph Angenendt <ra+centos@br-online.de> wrote: > >> Yes, IMHO a good idea. I already did that for pages which are for more > >> than one version of CentOS, see > >> <http://wiki.centos.org/Repositories/RPMForge> for example. > > > > I see. The key is to use = == === to index items on the page? > > = == === are different levels of headings - like h1 h2 h3 and so on in > HTML. [[TableOfcontents]] Then takes those headings and expands them > into a content table (which appears on the page at the point you add the > macro). > > Keep in mind: Even if you insert [[TableOfContents]] *after* some > headings, those will be taken into account. So normally you want to put > the macro near to the top of the page. > > Cheers, > > Ralph Done on the page above used as an example by KB. Thanks for the note. Akemi
On 7/3/07, Ralph Angenendt <ra+centos@br-online.de> wrote: > Akemi Yagi wrote: > > On 7/3/07, Ralph Angenendt <ra+centos@br-online.de> wrote: > = == === are different levels of headings - like h1 h2 h3 and so on in > HTML. [[TableOfcontents]] Then takes those headings and expands them > into a content table (which appears on the page at the point you add the > macro). A minor additional note. The macro uses this form: [[TableOfContents([maxdepth])]] ... and it does not work if the maxdepth is omitted. So it will be like [[TableOfContents([2])]] . Akemi