heksagonnet / piko Goto Github PK

Hi,

wonderful template. Is there a trick to install the website using RStudio, R and blogdown (See here https://bookdown.org/yihui/blogdown/a-quick-example.html)? After installing the website, it is neither loading nor properly rendered.

At least on my system

RStudio 2022.12.0 Build 353
R version 4.2.2
blogdown_1.16

On the example site I get this weird rendering of the metadata from the front matter of the blog posts:

Do you know what is going on here?

Hey there!

I seem to be having an issue embedding an image within a blog post. It appears that there is not an example on the demo site.

Can you please provide one in the demo? Or explain how it should work? As currently, I've used the methods that have worked before, and it doesn't appear to.

![]("/static/uploads/<filename>")

What do you think that caused that?
I'm running hugo on Windows 11.

The current version include in this has been deprecated by Google. What would it take to update to their latest analytic system?

Since your instructions differ significantly from the Hugo quick start guide, I am having problems customizing and deploying the site on my local server.

What works on the exampleSite is not reproducible on my own site.

Netlify blocks all new non-Pro accounts from signing up or logging in because of validation issues. So I am unable to try out the "quick way" either.

Here's what I did:

hugo new site wencai.io
Congratulations! Your new Hugo site was created in /home/sati/wencai/wencai.io.

cd wencai.io
git init
git submodule add https://github.com/heksagonnet/piko.git themes/piko

What next?

I see these files and folders in your exampleSite.

config.yml  content  netlify.toml  resources  static

which has some files and folders that are congruous to what I have on my project root:

archetypes  assets  content  data  hugo.toml  i18n  layouts  static  themes

When I replaced hugo.toml with config.yml, I get this:

This is as far as I can get, after hours of trial and error. Not sure what I need to do next. Copying content, resources etc. over from exampleSite to the root, replacing the original directories is a messy disaster.

Ideally, the documentation on README.md should guide us step by step to a stage equivalent to the Netlify deployment, where we are able to customize the site for our own needs.