chrisnmorrison / revista-gatsby-blog-magazine Goto Github PK

Many blog posts are about different topics (let's say "Sushi", "Vegan", "Rice") so we should be able to tag them with different values (afaik, we can only have 1 category per article).

This includes filtering by tag: if the users clicks "Vegan", they should be able to see only blog articles about that topic (ordered by date)

Since EU forces blogs to have a cookie banner, due to GDPR restrictions, I think it could be useful to add it to the template.

If I remember well, there's already an existing layout that you have to add to the page layout, so it should be easy to add (I suppose! )

Hello.

the theme works well if I use JPG files for cover images.

If I use png, it does not even compile.

Is it a matter of configurations?

Markdown tables are not being converted into HTML.

You can in fact see the plain text for such tables.

Do I have to install anything, or is it just not supported?

I'm migrating my blog to this theme.

I have my articles structured as

• posts
• • {type}
• • • {year}
• • • • {article number}-{article-name}.md

and each article specifies the final URL in a field in the FrontMatter section.

The article with FM like this:

title: "5 tricks every C# dev should know about LINQPad"
path: "/blog/5-linqpad-tricks"

Generates this page :
https://www.code4it.dev/blog/5-linqpad-tricks
Notice that the path does not reflect the folder structure

Now, after the migration, the page URLs must not change. Is there a way to generate page URLs reading from FrontMatter?

Hi.
I'm porting my blog to this theme.

There are around 130 articles, each with one cover image (well, actually there are some more, but I temporarily deleted them to try to fix this issue).

When compiling it, I used to see an error about heap allocation.

To solve it locally I had to increase the memory limit of the build process, updating the build command in the package.json file:

    "build": "cross-env NODE_OPTIONS=--max-old-space-size=16384 gatsby build --prefix-paths",
    "develop": "cross-env NODE_OPTIONS=--max-old-space-size=16384 gatsby develop",

Even with 16GB of memory, the build fails, as you can see from the logs here:
https://app.netlify.com/sites/thriving-lolly-25f944/deploys/641ad5eedb761b02e5be526e

Any idea on what can cause the memory leak?