Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Transclusion.

MoodleDocs talk:Transclusion

From MoodleDocs
Revision as of 14:31, 5 December 2008 by chris collman (talk | contribs) (→‎Partial transclusion example: tip3)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Partial transclusion example

Lets see if the following texts can be inserted into other pages via transclusion.

This text is only part of the text that is located on MoodleDocs talk:Transclusion page. Only this text should appear when {{:MoodleDocs_talk:Transclusion}} is inserted into another page.This text is after the onlyinclude but on the same line and this text may appear.

This text should not appear.

Here is some text from my user page.

I have contributed to MoodleDocs since 2006.

  • In 2010 I migrated a 1.5.3 production server to 1.9.x. We are scheduled to migrate that to 2.x in the summer of 2012. Most of my time is spent working with 3 small production servers running 2.1.x on an internal wan. I work in a training environmeent as assist trainers with blended learning technologies.
  • I moderate the Lesson and Certificate forums.
  • I am a sysop on all MoodleDoc versions, except the Dev namespaces.
  • While not a php or Moodle code developer, I have some knowledge of custom themes, certificates and have a few tricks I use to import a batch of images into a Lesson.
  • In 1.5- 1.9, I had knowledge of installing and troubleshooting Activity Locking (Conditional Activities). This is now part of a standard Moodle code (see advanced settings).


My MoodleDocs 2.1 page is here.

TIP 2: I could not insert a whole section from my user page called Test by using the # sign.

{{:User:chris collman/sandbox2#Test1}} put the whole page. Need markups

TIP 3: I could insert multiple onlyinclude markups and pick out selected text in a targeted page.

Cool beans! I think he has got it..The rain in Spain falls mainly on the plains! Just crawl, not run, towards the KISS --Chris collman 06:57, 5 December 2008 (CST)

Ideas

  • This can create footers and headers without use of special wikimedia CSS formats. I like the footer banner kind of idea but I know it can give a cluttered look.--Chris collman 08:21, 5 December 2008 (CST)
  1. Create a new FAQ namespace.
  2. In this namespace, create one page for each frequent question, where the contents of the page is the answer.
  3. Use our new knowledge of transclusions to build the FAQ lists by just pulling in pages from the FAQ namespace.

The benefits of doing this are

  • The same FAQ can appear in more than one list without copying-and-pasting.
  • Each question gets a unique URL that so in the forums, we can point people to a page that just answers their specific question.

Disadvantages

  • Editing FAQ lists becomes incomprehensible to anyone who is not a MediaWiki geek.

If we went this way, I would like to use B to build a new FAQ page: "Troubleshooting FAQ". Might be a good idea anyway. --Tim Hunt 07:11, 4 December 2008 (CST)