DEV Community

Cover image for Using Data with Hugo
David Large for CloudCannon

Posted on • Updated on • Originally published at

Using Data with Hugo

By Mike Neumegen

Brought to you by CloudCannon, the Git-based CMS for Hugo.

A data file in Hugo is sort of like a read-only database. The way it works is you can put JSON, CSV, YAML, XML, or TOML files in a directory called data, then access that data in a layout using .Site.Data. You can also download JSON or CSV files from an external source on build if you want to get fancy.

Creating your first data file

First we’ll create a data file with all of your favorite vacation spots. Create /data/vacation_spots.yml with the following content:

    - name: Masai Mara National Reserve
      latitude: -1.484751
      longitude: 35.101904
    - name: Serengeti National Park
      latitude: -2.333333
      longitude: 34.833332
    - name: Okavango Delta
      latitude: -19.304543
      longitude: 22.643703
    - name: Etosha National Park
      latitude: -18.855591
      longitude: 16.32932
    - name: Kidepo Valley Park
      latitude: 3.882778
      longitude: 33.874444
Enter fullscreen mode Exit fullscreen mode

What are Shortcodes?

To list your favorite vacation spots, you’re going to need:

  • Map software — you’ll use the fantastic OpenStreetMap and Leaflet.
  • A JavaScript list of markers — you have this in a data file currently
  • JavaScript to set up the map and markers
  • A div to hold the map

We could put all of this in a content file, but it’s going to be far more complicated than the simple markdown we have there currently. And what if we wanted to use this map again on another page? That’s a lot of HTML to copy and paste around.

Fortunately, Hugo has an answer, and it’s called Shortcodes. A shortcode is similar to a partial, except you use them in content files. Hugo even has a bunch already built in.

You’ll create a shortcode which can be used in any content file to create a map with marked locations. Let’s see how it works.

Your first Shortcode

Create a directory called shortcodes inside /layouts/ and add a file called vacation_spots.html with the following content:

    <div id="map">
    <link rel="stylesheet" href="" crossorigin=""/>
    <script src="" crossorigin=""></script>
      let markers = {{ $.Site.Data.vacation_spots }};
    <script src="/map.js"></script>
Enter fullscreen mode Exit fullscreen mode

There are a few things going on here, so let me explain:

  1. First we have the map element which will hold the map.
  2. Then we’re loading the stylesheet for Leaflet, which will help us create nice pins and pop-ups on the map.
  3. Next is the leaflet JavaScript file.
  4. Following that is the list of markers coming from your data file. Here it’s output as a JSON array.
  5. Finally we’re referencing /map.js which we’ll create shortly. This is responsible for initializing the map and adding the markers.

Let’s add the JavaScript to initialize the map and add the markers. Create /static/map.js with the following content:

    const map ='map');

        {attribution: '&copy; <a href="">OpenStreetMap</a> contributors'})

    let bounds = [];
    for (let i = 0; i < markers.length; i++ ) {
        const marker = L.marker([markers[i].latitude, markers[i].longitude]).addTo(map);
        bounds.push([markers[i].latitude, markers[i].longitude]);

Enter fullscreen mode Exit fullscreen mode

We’re not here to learn JavaScript so I’ll leave this one for you to decipher (or not).

The final set is to actually use the shortcode. Open up /content/ and append the following:

    ### These are my favorite vacation spots

    {{< vacation_spots >}}
Enter fullscreen mode Exit fullscreen mode

Open it up in a browser and admire all your hard work.

What’s next?

This is only the beginning of your Hugo journey. You now have the skills to build a basic Hugo site. To continue the journey there’s a few resources I recommend:

Finally I want to quickly mention CloudCannon - it’s a content management system with first class support for Hugo and syncs directly with your Git repository. So your developer team can continue working in Hugo while your content team can manage the content on the site. It’s the best of both worlds.

Thanks for reading and Happy Hugoing!

Top comments (0)