Using index.md without getting a page index?

[jhagg]

I have a directory ('mytest') with a index.md file, but if I go to 'mytest/' or 'mytest', I get a page index with one file, 'index'.
Is it possible to jump to the index.md directly, without going through an index list?
Or have I just missed some configuration entry? :-)

[starkmarkus]

I do not think index.md currently has special “directory index page” semantics in OtterWiki.

From what you describe, OtterWiki is treating:

mytest/index.md

as a normal wiki page named mytest/index, while:

mytest/

is treated as the directory/page-index view for that path. So instead of automatically rendering mytest/index.md, it lists the pages below mytest, which in your case is only index.

So the direct page URL would be something like:

mytest/index

rather than:

mytest/

I could not find a configuration option that makes index.md behave like the default page for its containing folder.

So I think the current options are probably:

• link directly to mytest/index;
• avoid using a folder if you only want one page;
• create the page as mytest.md / mytest instead of mytest/index.md;
• or open this as a feature request for “directory landing pages” / “treat index.md as folder default page”.

If implemented, the behavior would probably need a clear rule for what happens when both a page and a directory exist, for example:

mytest.md
mytest/index.md
mytest/other-page.md

So my current answer would be: no, this does not seem to be configurable right now; index.md is just a normal page, not an automatic folder landing page.

[jhagg]

So, to use a subdir xxxx, I have to create xxxx.md in parallell to xxxx and
create links in xxxx.md as [[xxxx/abc]] and [[xxxx/def]]?

Could this behaviour perhaps have something to do with attachments?

I was hoping I could create an index page with some name, be it index.md or
xxxx.md in subdir xxxx, where I could just add the links [[abc]] and [[def]]
without the xxxx prefix.

Like this:

xxxx/
	index.md or xxxx.md
	abc.md
	def.md

[starkmarkus]

I think there are two separate behaviors here:

1. What page is shown for /xxxx/
2. How links inside that page are resolved

For the first one, yes, with the current behavior it looks like /xxxx/ is the page-index view for the folder, not an automatic render of /xxxx/index.

So if you want a landing page for that section today, the current workaround is probably either:

xxxx.md
xxxx/abc.md
xxxx/def.md

with links like:

[[xxxx/abc]]
[[xxxx/def]]

or:

xxxx/index.md
xxxx/abc.md
xxxx/def.md

but then the direct page is:

xxxx/index

not:

xxxx/

For the second part, I would not assume that wiki-style links like:

[[abc]]

are resolved relative to the current page folder. In many wiki systems they are treated as wiki page names/paths from the wiki root. If OtterWiki behaves that way, then [[abc]] from xxxx/index.md would point to abc, not xxxx/abc.

So your desired structure:

xxxx/
  index.md
  abc.md
  def.md

with index.md containing:

[[abc]]
[[def]]

would need either relative wiki-link support or special folder-index semantics.

I do not think this is related to attachments. It sounds more like OtterWiki’s current routing/model:

folder path  -> page index
file path    -> page

A feature request could probably combine both wishes:

1. Treat index.md as the default page for its folder.
2. Resolve [[abc]] relatively inside xxxx/index.md, or provide syntax for relative wiki links.

Until then, I think the safe option is to use explicit links like [[xxxx/abc]], or test whether normal Markdown links such as [abc](abc) / [abc](./abc) behave relative to the current page in your setup.