Inserting a code block with linenos turns it into a table.

From the zola documentation on Syntax Highlighting:

When line numbers are active, the code block is turned into a table with one row and two cells. The first cell contains the line number and the second cell contains the code. Highlights are done via the HTML tag. When a line with line number is highlighted two tags are created: one around the line number(s) and one around the code.

As you can see from the examples below, the styling does not look great for a code block. Would it be possible so that code blocks to not have this styling applied to them? I noticed that when you have a code block, regardless of whether it has line numbers enabled or not, it is wrapped in <pre> and <code> tags. Not sure if this is helpful but it is different than tables which are not nested in other tags.

Without linenos

```python
try:
    from jupyter_client.kernelspec import install_kernel_spec
except ImportError:
    from IPython.kernel.kernelspec import install_kernel_spec
from IPython.utils.tempdir import TemporaryDirectory
```

With linenos

```python,linenos
try:
    from jupyter_client.kernelspec import install_kernel_spec
except ImportError:
    from IPython.kernel.kernelspec import install_kernel_spec
from IPython.utils.tempdir import TemporaryDirectory
```

It seems to be a problem when uri has path.

e.g., when uri is example.com/blog, it should get fonts from example.com/blog/assets/fonts/some-font.woff.
but it sends request to example.com/assets/fonts/some-font.woff and receives HTTP 404.

You may want to visit my page for details. (that hasn't any contents)

index.html's main block invokes the list_pages macro which references paginator.pages which, out of the box, does not seem to exist:

$ zola serve
Error: Failed to render section 'content/_index.md'
Reason: Failed to render 'index.html': error while rendering macro `lists::list_pages`
Reason: Variable `paginator.pages` not found in context while rendering 'macros/lists.html'

I am using zola 0.12.2 and zerm 5ca1968a1a88660aa23c8dc51bc9994bb9fdfceb.

Is this a zerm issue or did I miss a required configuration option (or global(?) frontmatter)?

It seems that code blocks currently default to word-wrapping the text horizontally instead of allowing the reader to scroll left and right. This means that code samples published with this theme that drift rightward end up being wrapped, breaking their formatting and readability. This could be fixed by adjusting overflow, I think?

things that should probably be added:

• credits to major contributors
• enumerating all features
• explicit documentation for more complicated/niche features

Nothing is broken AFAIK, but this theme has fell behind Zola's API before and I'd like to prevent that.

it would be nice for users to have a straight forward guide that explains a viable blog structure/setup for using this theme out of the box. things have probably changed since i first published the theme, etc.

Cloned zola repo and just did zola serve

The code highlighting is not working.

See discussion in #23.

As it exists, you can't add URLs to external sites to the menu using the existing config options and templating logic because the base URL, example.com etc, is always prepended.

Inline code (`like so`) has white-space: normal set, which makes it break:
like
so

instead of carrying over to the next line.
like so

I see there's a 'comments.html' macro available. How would someone go about putting a disqus snippet in there properly with your template?

Thanks.

it would be nice if the templating for enumerating tagged/categorized posts ignore any given post with draft set to true. this would mean that someone could publish on their blog drafts and be able to link to it without worrying about it being seen by the public before its ready.

After messing around with Zola 0.14, I think there's an incompatibility due to how we were referencing the default language before.

Looking at the changelog, it appears that the config object has been stripped down.

I haven't had a chance to do more debugging yet, but I wanted to open this issue to raise awareness. I'll likely take a crack at fixing it myself soon, but not sure when that will be just yet.

Edit: I think that we can just switch this to lang instead of config.default_language but I'm not sure yet without trying.

Hey @ejmg ,
I am trying out this theme for my website. One thing I would like to know is creating a 404 page. I tried out what was given in the zola docs, but I get this error:

Error: Failed to render '404.html' (error happened in a parent template)
Reason: Variable `current_path` not found in context while rendering '404.html'

I placed the 404.html file in the templates/ directory, with the following content:

{% extends "index.html" %}

{% block content %}
    <div class="post">
        <h1 class="post-title">404: Page not found</h1>
        Sorry. non-existent
    </div>
{% endblock content %}

Is there anything else I should do? Can you please help?

zola serve fails because of show_author = true even though config.extra.author = "papojari". With show_author = false it works.

➜ zola serve
Building site...
Checking all internal links with anchors.
> Successfully checked 0 internal link(s) with anchors.
-> Creating 16 pages (0 orphan), 3 sections, and processing 0 images
Error: Failed to render section '/git-repos/papojari.codeberg.page/content/authors/_index.md'
Reason: Failed to render 'section.html': error while rendering macro `posts::section_meta`
Reason: Macro `author` is missing the argument `page`

Hello,

I would like to know how to create a link to an external site in the menu, looked at the sample configuration files but I can't find a way. $BASE_URL always prepend...

Thanks in advance!

here's a good article to get an idea of what this looks like.

largely, i think it would mean turning any instance of pagination to use article elements for each blogpost enumerated, and using header correctly for each... well... title header.

#5 brings up the fact i was lazy and never got around to upstreaming a 404 page for zerm. that should be fixed.

I think the demo of this blog theme would be better if it was Pius-themed.

Hello,

I couldn't get Code block syntax highlighting to work. i.e. text in the entire code block has the same colour.
I have cloned a zerm from scratch, ran it without modification / with different themes, the behaviour persisted. Is this intended?

zerm:

What I'd expect:

Thanks for the amazing project, have a nice day :)

Hello,

I don't know if this is normal, but the extended_header macro is never used in the index template (or any other template)? Could you explain why? Am I missing something?

Thanks for this amazing theme!

Here's the offending template code.

Looks like I should be doing piping the summary/description to the markdown filter or something similar to that.

Otherwise, stuff like this happens:

Hi, thanks for making this!

I cannot get these theme to render. I have tried forking the repo, also tried the instructions of adding this theme to existing repo, but both fail with errors like:

Error: Failed to render section '/home/pfes/my-app/content/_index.md'
Reason: Failed to render 'index.html': error while rendering macro `head::styling`
Reason: Function call 'get_url' failed
Reason: `get_url`: Could not find or open file style.css