Editing Best Practices (to avoid release errors)
Always use Relative Wiki Links!
When entering in links to other pages in this wiki, never use the Full Harcoded Link. Instead, always use a relative link!
For example, if you wanted to link to the Configuration page:
Harcoded Link (BAD!) |
https://wiki.duraspace.org/display/DSDOCDEV/Configuration![]() |
||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="58c6b74f-28a0-42b3-bd45-7820ce77c832"><ac:plain-text-body><![CDATA[ |
Relative Link (Good!) |
|
]]></ac:plain-text-body></ac:structured-macro> |
Another example! This time, of a link to a specific heading on a page. Suppose you wanted to link to the Batch Metadata Editing header on the Configuration page:
Harcoded Link (BAD!) |
https://wiki.duraspace.org/display/DSDOCDEV/Configuration#Configuration-BatchMetadataEditing![]() |
||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7538a690-d3e7-402b-9f13-9c11137156df"><ac:plain-text-body><![CDATA[ |
Relative Link (Good!) |
|
]]></ac:plain-text-body></ac:structured-macro> |
One final example. It's the same as the above "Batch Metadata Editing" example, but now we are changing the text in the link to say "Configuration for Batch Metadata Editing"
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c0d3e9b7-8ba5-4138-b3aa-a882b0b495ff"><ac:plain-text-body><![CDATA[ |
Harcoded Link (BAD!) |
[Configuration for Batch Metadata Editing|https://wiki.duraspace.org/display/DSDOCDEV/Configuration#Configuration-BatchMetadataEditing] |
]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b004a8b1-aec6-43d4-86ae-1a7193f279e1"><ac:plain-text-body><![CDATA[ |
Relative Link (Good!) |
|
]]></ac:plain-text-body></ac:structured-macro> |
You can view the source of this page for examples
Use our standard Table of Contents when creating a new page
In the Official DSpace Documentation, we try to use a standard "table of contents" on each and every page (it's even at the top of this page).
Here's the Wiki code to create that standard Table of Contents (just replace "<PAGE NAME>" with the name of the page)
h1. DSpace System Documentation: <PAGE NAME> {toc:outline=true|style=none|minLevel=2}
This table of contents does a few things:
- starts the page off with an <H1> heading (all headings after that should be h2. or h3. or h4. , etc.)
- formats the TOC like an "outline" (1, 1.1, 1.2, 2, 2.1, etc.)
- turns off any special styling
- Ensures the TOC skips over the first <H1> heading and starts at all headings below it.
For an example, just view the Wiki Markup for this page!
There may be occasional exceptions to this rule. One example is the Upgrading a DSpace Installation page, which uses a bulleted-list based Table of Contents (as the outline numbers look confusing next to the DSpace version numbers).
Additional General Wiki Syntax Hints
Some general Wiki Syntax hints/tips can be found in our DSpace Wiki Style Guide.
Obviously, just clicking "Edit" on any wiki page (and especially looking at the "Wiki Markup") is a great resource as well!