Vincent Prouillet
Vincent Prouillet
I don't really want to add that dependency or a command just for that. I think it's something that should stay in a fork of the person maintaining the schema
It works for me? What's your config like
I get ``` ~/C/p/zola-test $ zola check Checking site... Checking all internal links with anchors. > Successfully checked 0 internal link(s) with anchors. Checking 2 external link(s). Skipping 0 external...
The broken internal links is resolved when rendering the markdown. Anchors errors are reported after all the md have been rendered. We could delay the rendering errors but we don't...
> I wonder, what's even the point of having @? > Why not automatically treat any internal link as one that should be checked? `@` links refer to the markdown...
Related: https://github.com/getzola/zola/pull/2869 I'll take a PR for it
The idea with Validation was really that you keep them around so it was not designed with that kind of optimization in mind. The trait approach would be better but...
If the content is full HTML, you can just create a .md file and put your HTML content preprended by `+++\n+++` and that should work? Assuming it's meant to go...
You could wrap them in a markdown shortcode with a `hidden` param or something.
How about adding width_unit and height_unit as new fields or have new fields that are width + unit as Option?