Trouble querying content with 11ty

Heya, I’m trying to make my first site using sanity. I want to use Eleventy as my frontend but I’m having trouble querying the content from my database. Are there any specific guides for eleventy and sanity?

Hi Ben, welcome! 👋 And cool choice with Eleventy (we recently opened an 11ty channel in case you want to join). There’s an Eleventy + Sanity blog boilerplate example over here: https://github.com/kmelve/eleventy-sanity-blog-boilerplate
Are you getting any specific errors when querying content?

There's also this “just add water” thing 🙂 https://www.sanity.io/create?template=sanity-io%2Fsanity-template-eleventy-blog

Thanks! I haven’t had a look at the boilerplate one so I’ll check it out

the error I’m getting is this one

"Unable to parse entire expression"

Do you have any repo you can share (in DM if you prefer)? Or specific code causing that error if it’s clear where it comes from?

Do you have any repo you can share (in DM if you prefer)? Or specific code causing that error if it’s clear where it comes from?

There's also this “just add water” thing 🙂 https://www.sanity.io/create?template=sanity-io%2Fsanity-template-eleventy-blog

Thanks! I haven’t had a look at the boilerplate one so I’ll check it out

the error I’m getting is this one

"Unable to parse entire expression"

Heres a link to the repository https://github.com/benjaminearl/informal-justice-court

Thanks Ben! Did it originally work when you made the initial commit? You used Sanity’s 11ty starter for this, correct (the one Knut shared)?

No I started with a clean sanity, structured the database and then was beginning to figure out how to get the data to eleventy which is where I got stuck. But I did have a look at the one that Knut shared to try and help me

In

newsItems.js

}

const projection = groq `{
  _id,
  publishedAt,
  title,
  body
  }
}`

const projection = groq `{
  _id,
  publishedAt,
  title,
  body
}`

ahhh sneaky! Thanks, I’ll check it

Hey, sorry to keep bothering you. The bracket was indeed the problem but now I’m having trouble previewing the rendered html content in eleventy. When I run

npx @11ty/eleventy --serve

Cannot GET /

I switched to using the boilerplate that Knut sent above but adjusted everything for my site

Does your web root have an

index.njk

layout: layouts/home.njk

home.njk

_includes/layouts/

Also, do you have this section in the return statement of your

.eleventy.js

dir: {
      input: ".",
      includes: "_includes",
      data: "_data",
      output: "_site"
    }

yes to all of the above!

here is the repo: https://github.com/benjaminearl/test-sanity-eleventy-site/settings

I’ve tried deploying it to netlify but thats also having issues too

The latter would make sense as it might be lacking some Netlify-specific config. It seems to be set up for Vercel (previously known as Zeit Now) - see the

now.json

yeah thats great, thanks for your help!

What’s the error you’re getting on Netlify?

its managing the deploy alright but then when I open the studio page sanity stays on the loading screen until it says that there might be a problem with the internet connection

When I run eleventy from inside the web folder then it works, but from the root it doesn’t

Hi again Ben, just had some time to go through the repo. Have you tried something like this in your

newsItemsList.njk

<ol reversed class="newsitemslist" style="counter-reset: start-from {{ newsitemslist.length + 1 }}">
{% for newsItem in newsitemslist | reverse %}
  {% set currentNewsItem = newsItem.data.newsItem %}
  <li class="newsitemslist-item{% if newsItem.url == url %} newsitemslist-item-active{% endif %}">
    <a href="{{ newsItem.url | url }}" class="newsitemslist-link">{% if currentNewsItem.title %}{{ currentNewsItem.title }}{% else %}<code>{{ newsItem.url }}</code>{% endif %}</a>
    <time class="newsitemslist-date" date="{{ currentNewsItem.publishedAt }}">{{ currentNewsItem.publishedAt|readableDate }}</time>
  </li>
{% endfor %}
</ol>

ah I can’t believe I missed that I hadn’t changed ‘post’ to ‘newsItem’

thank you, it worked perfectly

Awesome! 🙂