Skip to content

Commit 6c0938e

Browse files
authored
Create README.md
1 parent 387a649 commit 6c0938e

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

README.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# raw-test-git
2+
3+
This blog project is running on my local machine with Eleventy v0.12.1 and Node v14.16.1
4+
5+
---
6+
7+
Purpose of this project:
8+
9+
I have two separate directories, one is /sights/ the other one is /sounds/. I want to run them indipendetly, each one with its own tags.
10+
11+
I want Eleventy to build:
12+
13+
/sights/tags/(all tags for sights);
14+
15+
/sounds/tags/(all tags for sounds).
16+
17+
But instead I get:
18+
19+
/sights/tags/(all tags for sights and sounds);
20+
21+
/sounds/tags/(all tags for sounds and sights).
22+
23+
---
24+
25+
Raymond Camden (Thank you very much Raymond), noticed that both tags pages are still paginating over collections, not collections.sights or collections.sights;
26+
once I've tried to resolve the pagination as above - which is the right change - I get errors.
27+
28+
Raymond noticed that this is because it's exposing another error: the issue is that permalink, as I have it, cannot use dynamic data like that,
29+
and he suggested a workaround: to use eleventyComputed to define the permalink (https://www.11ty.dev/docs/data-computed/#using-a-template-string).
30+
31+
After several attempts there are still errors. Is clear that the problem is my incompetence in how to remove the dynamic value from the front matter.
32+
33+
You can see my original question and suggestions from Raymond Camden on:
34+
https://stackoverflow.com/questions/68814674/eleventy-11ty-tag-list-sorting-for-2-independent-directories
35+
36+

0 commit comments

Comments
 (0)