-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
feat: support creating collections #185
Comments
通过文件夹结构(是否在一个文件夹下)或 |
对于用户来说, |
是的,就是通过类似于这样子的形式来判断是否属于一个合集,categories 书写进整个合集的配置当中,将整个合集分进同一个 categories。 |
如果没有合集的话, |
同时比如说对于合集的话可以在原先的 TOC 位置进行切换,选择现实本帖子目录或者合集帖子列表。其次就是单独写个页面展示合集内文章的界面。比如在 archive、categories、tags 这样子的页面可以只显示合集名称,点进去之后是合集里的帖子列表;在主页可以将最新帖子的标题、时间、相关概述进行显示,并且标注这是在合集中的帖子,然后点进这个帖子的时候直接跳转到此文章。 至于合集文章的排序我觉得可以按照最新更新时间或者用户在每个合集里的帖子的 frontmatter 自己定义 order。 |
这仍然属于 posts 的一种形式吗?它在页面上的展示效果仍然与 posts 相同吗?是否应该以 |
我认为除了在 aside 添加合集目录,其余的页面展示上没有什么区别。可以使用 |
我认为 |
如果不存在必须放置于 当然,在此之前,我觉得需要询问是否存在一些反驳(放在 |
我认为可以直接放在 |
I always want to write a series of posts like serial novels, serial tutorials and so on. So maybe Valaxy can add a collection feature to put these posts together. The struction of collection is just like a novel, which has chapters (even has volumes). Here are some detailed functions I want:
collection.yaml
to config this collection.Next, I will talk about the functions above.
For the first function, the struction of
posts
folder is like this:And when I create
collection.yaml
in a subdirectory ofposts
, I hopeValaxy
can identify this folder as a collection andcollection.yaml
is like this:Similarly, creating
collection.md
and put these settings in the frontmatter is okay.For the second function, (the house icon means a collection)
Of course I can put serial posts in the same catagory, but every post is shown like this:
And the second thing is that a series of posts belongs to the same category and tags, so it is troublesome to set or modify category and tags for every post.
Well, in summary, collection feature is like this:
The text was updated successfully, but these errors were encountered: