go-github | Go library for accessing the GitHub v3 API | REST library

I'm not sure what you meant exactly by:

type from the response cannot be unmarshalled

Did you receive some kind of an error?

The call to ListReleases returns a []*RepositoryReleases (see code), so you can loop through the response and do whatever you need to with the data.

For example, to list the name of every release:

I'm Not Sure how GitHub pages are configed however they probably have cross-scripting disabled since it is a major security risk. When disabled third-party dependencies won't work often. so if your animation depends on any script outside the server then it won't work it could also be that the file structure changed when being uploaded.

I would start with an interface:

You should cover tag not tag. What you are doing is tag doesn't take any space so it has no width or height. That is the reason why you can click on it so it doesn't work.

Just move it? I'm somewhat sure it's not the best solution, but still.

update props name

With certain assumptions like you are storing json data in your cache below is how I will try. Errors not handled.

I am not good at using the debug tools, so just stepped through the code. (Appreciate the suggestion of good tutorials!)

First things first: When in Doubt, Try to Upgrade Your Software Packages This is the blogdown package creator's advice. Checked.

1. Launching the addin, blogdown:::new_post_addin is called.
2. This calls new_post.R. The source code can be find at: https://github.com/rstudio/blogdown/blob/master/inst/scripts/new_post.R
3. blogdown::new_post() is called at the end, with file parameter from the updated input text field, which is in the case of the question: "post\2020-11-04-how-this-site-was-created\index.en.md"
4. new_post() function (in hugo.R) calls new_content() with the third argument, open = FALSE, which means it will not open the file, just overwrite the value of the file variable (the path hereafter). At the end of new_post() the file should be opened: this is where the error occurs (by trying to open the file at the wrong place, a wrong path). This means that something bad has to happen in new_content().
5. new_content() modify the path with content_file(). Also this is the step, where the file is actually created.
6. content_file() modify the path by adding a prefix to it generated by get_config().
7. get_config() tries to extract the value of a field in the configuration, in the case of Hugo: try to find contentDir. If this results in NULL (there's no such list item), then see the other possibility and lastly return the default value (which is in the case of Hugo: content). And that's it! RStudio tries to open a file in the content directory, not in a language subdirectory!
8. That means that the last option is returned in the row of %n% (which is imported from knitr and stands for: if (is.null(x)) y else x). That means that the previous arguments returned NULL, which means contentDir cannot be found in config variable. The default value of config is set by config = load_config(). This uses find_config() to find the config file to parse.
9. find_config() uses config_files() to set the value in case of Hugo: c('config.toml', 'config.yaml'). But my setting is in a subdirectory: in the /config/default_/languages.toml file! Oh, another Academic theme woe...

To conclude this: blogdown is currently loads only the config.toml in the root directory to check the contentDir value. The Academic, now Wowchemy Hugo theme however keep config files in the /config/default_/ directory also, where the languages.toml contains the needed value.

To keep or not to keep Academic theme? Stick with blogdown or not? Maybe the config files should be merged into one config.toml, but couldn't find hint or examples for Academic on the web.

Edit: OK, the root of the problem has been found, but the actual error which raised the error message is in connection with hugo_convert_one(), as the traceback suggests in the question. This was the first (and last) try to open the file of the wrong path.

Fixed this way in post.html