-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Release 1.0 #27
Comments
I found blades when I was looking for a quick Rust-based static site generator. It's cool, but there's a problem. To put it simply, sections do not know anything about subsections
Nothing wrong with posts, but reviews also look like end section, no links to the nested books or movies. Breadcrumbs don't work properly too. For the page |
The issue with incomplete breadcrumbs is a bug, I just submitted a fix in 1cb447e. |
Thanks, that was super quick. I'm going to try and make a blog for myself this weekend. Another suggestion. I have a bunch of posts grouped into dirs, mostly how-to guides. I don't want to add extra files like index.md. It would be really nice if Blades could use the name of the parent folder as the section title if there is no index.md in it. After all, "linux-guides" or "recipes" is better than nothing. Just a nice thing to have. Although potentially problematic (removing invalid characters and stuff). P.S. I don't understand anything about the web and generators under the hood, so if my suggestions are crazy, just ignore them. |
That is what Blades already does :) |
Do I need to use some special settings to make it work? I haven't looked into it closely, but it doesn't happen by default for me. Yes, Blades creates an index file on the fly, but without a title. Maybe we just had a bit of a misunderstanding. I use default minimal theme (42f0e71), my test content: example-content.zip
Left: actual result with example content | Right: real index.md is present |
Alright, published 0.6.0 |
Blades seem stable to me now to mark the next release as 1.0,
It would probably make sense to wait for maciejhirsz/ramhorns#75 to be merged, so that we can use upstream Ramhorns.
Any feedback on current stability and desired features/improvements/breaking changes is the most welcome, to make this release as robust as possible.
The text was updated successfully, but these errors were encountered: