If by /views you mean root, then I have an index.njk file. Eleventy turns that (and all other md files) into index.html. I guess I just don't get how to get from that, to something which will actually work when I deploy it. I am used to files called about.html, contact.html, etc, but I guess the 11ty server has a way of making sense of similarly named files with different paths? I actually have a feeling this can be fixed with permalinks somehow, but again, this is not explained too well at 11ty.dev. Hmm... but thanks for your answer!
I am a tall (1,95m) coding & drawing enthusiast that likes all type of coding and drawing cartoons. I like to work (coding & drawing) on the go with my surface
#cypress #js #csharp
It's kind of hard to explain :-)
I see your links look like this: "about/index.html"
While mine look like this: "/About" or "/posts/2020/blog-post-3/"
My links work locally, but not on my remote server. It makes sense to me now, that there should be a html file at the end of that string, but I'm new to this SSG-thing, so everything looks strange to me ;-). But did you set those link urls manually? That would seem inefficient...
I am a tall (1,95m) coding & drawing enthusiast that likes all type of coding and drawing cartoons. I like to work (coding & drawing) on the go with my surface
#cypress #js #csharp
Hi,
In my case "/about" would also work, because the HTTP server usually knows that it must serve a file called "index.xyz".
But if you using "/About" but your file is named "about.njk" then it will work locally on your windows (if you have one) but not on your remote server (that probably is a linux server) because of the casing of "A".
The links in this simple example are manually added. But this does not matter I think.
"/posts/2020/blog-post-3/" should also work if there is an index.html file located within that folder. Maybe the setting of your remote http server is wrong and it does not know anymore what file should be served?
Hmm, yes, that makes sense. I read up on links: w3.org/Provider/Style/URI.html and I'm starting to understand the 11ty file/folder structure. But perhaps my server doesn't get it ;-)
Figured it out! I started an issue (closed now - yay) about the whole thing, and finally was able to wrap my head around what I was doing right and wrong. Thanks a lot for your time as well - you got me on the right path to the answer(s)! Here's the issue, btw: github.com/11ty/eleventy/issues/1045
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If by /views you mean root, then I have an index.njk file. Eleventy turns that (and all other md files) into index.html. I guess I just don't get how to get from that, to something which will actually work when I deploy it. I am used to files called about.html, contact.html, etc, but I guess the 11ty server has a way of making sense of similarly named files with different paths? I actually have a feeling this can be fixed with permalinks somehow, but again, this is not explained too well at 11ty.dev. Hmm... but thanks for your answer!
I am not sure if I understand what you mean :-)
Please have a look at this example: github.com/gabbersepp/11ty-example
Feel free to make a pull request to show me an example of your code :)
It's kind of hard to explain :-)
I see your links look like this: "about/index.html"
While mine look like this: "/About" or "/posts/2020/blog-post-3/"
My links work locally, but not on my remote server. It makes sense to me now, that there should be a html file at the end of that string, but I'm new to this SSG-thing, so everything looks strange to me ;-). But did you set those link urls manually? That would seem inefficient...
Hi,
In my case "/about" would also work, because the HTTP server usually knows that it must serve a file called "index.xyz".
But if you using "/About" but your file is named "about.njk" then it will work locally on your windows (if you have one) but not on your remote server (that probably is a linux server) because of the casing of "A".
e.g. kack.dev/1/index.html works but kack.dev/1/ works, too. The server delivers the same page for both links.
The links in this simple example are manually added. But this does not matter I think.
"/posts/2020/blog-post-3/" should also work if there is an index.html file located within that folder. Maybe the setting of your remote http server is wrong and it does not know anymore what file should be served?
Hmm, yes, that makes sense. I read up on links: w3.org/Provider/Style/URI.html and I'm starting to understand the 11ty file/folder structure. But perhaps my server doesn't get it ;-)
Figured it out! I started an issue (closed now - yay) about the whole thing, and finally was able to wrap my head around what I was doing right and wrong. Thanks a lot for your time as well - you got me on the right path to the answer(s)! Here's the issue, btw: github.com/11ty/eleventy/issues/1045