Currently I have been creating individual files for each book I read. This results in a huge amount of frontmatter per book and makes it complicated to add a new book. Since there is no way to automate filling in this front matter using hugo new I am looking at using my Goodreads export file (in CSV…

What you want is not yet possible, but there is an open GH issue about it: https://github.com/gohugoio/hugo/issues/5074 Now, if you were okay with having all your book info on a single page, that is very doable. It’s the “build a new page for each book” that is not yet possible.

I would create a separate script in your favourite language to read the CSV file and generate separate content files with the needed frontmatter filled in. Hugo would then see the content files and generate the site as you want.

You can (probably easily) convert the csv to json. And hugo accepts json for build right now.

I like the JSON idea, but in the docs it says this: “Data files aren’t used to generate standalone pages; rather, they’re meant to be supplemental to content files” So I’m not sure if that would allow what I’m trying to do…

@frjo I already have a separate file for each book, generated from the CSV using Wordpress, a plugin, and Advanced Custom Fields. Just trying to automate the workflow a bit going forward.

[image] dixonge: The workflow I envision is to add an entry to the CSV file, then have hugo create the resulting html file during the build process (or using LiveReload locally). We’re not there yet. That would be an ideal scenario but as @zwbetz mentioned hopefully this will be possible once…

In retrospect, even though it wouldn’t take long, I’ve decided that rebuilding 140+ book pages every time I change something on the site feels pretty clunky. As a workaround, I added ‘newContentEditor’ to my config file so any new book page created auto-opens in VS Code. I have the archetype set up…

[image] alexandros: Currently the way I am creating separate Markdown files from a CSV is outlined here: Work-around for making pages from data? support Ha! Thanks so much for that @bep +1 I wouldn’t have thought of using Hugo environment variables this way! @gaetawoo Here is a working examp…

By JSON I mean create a markdown file with json in it. So the extension will be .md but whatever is in the file is json (as opposed to yaml or toml). This is for your posts in your content folder. Whatever is in the data folder is something else entirely. That’s what you are referring to @dixong…

Here is a simple example of a python script that converts each row in a CSV file in to a Hugo post. It will use the first row as headers and use them as params in the front matter. If a file exist it will not be regenerated, this speeds up the script if you are adding to the CSV file and want to o…

[image] dixonge: Just for clarification, how do you trigger the file creation? Do you have to run ‘hugo new’? Normally you have to provide a filename with that… Indeed. Typically I paste a list of hugo new commands in the console and the files are created sequentially. env HUGO_TITLE="110" …

Using CSV file to create individual posts on build

support

dixonge June 5, 2019, 8:59pm 9

Just for clarification, how do you trigger the file creation? Do you have to run ‘hugo new’? Normally you have to provide a filename with that…

Topic		Replies	Views
Creating Files from Data (like Product pages) support	12	4563	January 23, 2019
Work-around for making pages from data? support	31	10353	February 16, 2025
CSV/JSON files as basis for posts support	11	1379	December 2, 2021
A simple example to create a csv file support	3	170	November 15, 2024
Generate from mysql data to Hugo support	4	2008	October 6, 2019

Using CSV file to create individual posts on build

Related topics