Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: Why stick to .page extension #9

Open
michelk opened this issue May 23, 2014 · 1 comment
Open

Discussion: Why stick to .page extension #9

michelk opened this issue May 23, 2014 · 1 comment

Comments

@michelk
Copy link
Sponsor

michelk commented May 23, 2014

I'm wondering what is the benefit of using the .page-file-extension in combination with the header

---
format : whatever

---

Isn't it simpler to choose the reader based on the file-extension (.md, .org, .html, .tex, .rst, ...)? Links then still look the same; but gitit has to look for the first occurrence of the basename of the file. For example

Here comes the [link](blah).

with blah.md to find.

@jgm
Copy link
Owner

jgm commented May 28, 2014

The idea was to have a simple mapping from URL to file.
Otherwise gitit would have to make multiple queries of the
filestore each time a page is requested (first trying .md,
then .rst, then .html, etc.).

Also, I had thought that people might want to include org,
md, rst, etc. files in their repositories as regular files,
not to be rendered as wiki pages. The present system gives
them a choice: if it's .page, it will be rendered as a wiki
page, and if it's .html, it will be rendered as an HTML upload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants