For example, on this blog I currently have two “types” of content;
BlogPost is any file found in my
sylvan/content/blog directory and it will be accessible from the
/blog/ endpoint. Likewise
BookReview content is found in
sylvan/content/book. Each content type has it’s own iterate that you can import to loop/map/find/etc. over and is also located in the
Where Content Layer is going to really shine is when I figure out how to hook
sylvan up to my knowledgebase and then exclude some files from being generated into content — for example maybe I don’t want to import my work-related documents into my personal website.