hugo-site VS JSONFeed

This month, I took my site squarely into npm-ville when I brought in the npm version of Sass and added PostCSS to make "future" CSS work with current browsers. As it turns out, those changes made my site an unexpectedly appropriate target for the use case that Hugo Installer presents. I’m sure I’ll find nits to pick over time but, for now, I’m impressed by what I’ve seen.

Fortunately, while there are limits to how much you’ll be able to improve your experience with online search in general, you can optimize your own website’s search capabilities. That’s assuming, of course, that your website is built with a static site generator (SSG), as I’ve recommended on my own website over the years, and has search capabilities in the first place. If it lacks search, you can fix that readily enough with the free Pagefind tool about which I wrote earlier this year.

In Line 2 of the partial that I use for the search bar and results, I comment out the line of code that calls to the Pagefind CSS. (I derived it from the Pagefind documentation.) It's this step for which I can't find the corresponding code in your repo, but I'm sure you know where it is; and that's the key to this.

(a.) My own site, https://www.brycewray.com --- currently hosted on Cloudflare Pages, although it's also been on other Jamstack hosts such as Netlify, Vercel, and (briefly) Render.

although I (b.) also sometimes put stuff on dev.to.

Thanks! I will at some point. The code — in its current, very “as-is” state — is in my repo at (as of now) https://github.com/brycewray/hugo_site/blob/main/layouts/partials/webmentions-pipes.html if you can bear its spaghetti-ness. But, assuming you mean you’ll want a walk-through explanation: yes, that’s yet to come. There are some things I need to refine, first.

When I have the code somewhat DRY-er, I’ll write about it. In the meantime, I’ve left the following comment within the webmentions-pipes partial template I’m using to suck all this into each applicable post, just in case the curious happen to find that partial on the site repo:

By Bryce Wray

Having just moved my own site to Astro yesterday after a week or two of experimentation and grunt work, I can offer some opinions which may help you with that question. I’ll go through the “boxes” which I believe any SSG or other website development platform should “check” before you should give it a shot at this task, along with how I judge Astro’s ability to do so in each case.

If you have a web feed, be it RSS or Atom or JSON Feed, help others discover it!

Imagine you have an RSS feed similar to this. The objective is to obtain that RSS feed, analyze the data it contains, and take action with it. RSS is an XML format, whereas JSON is arguably easier to work with than XML. While many APIs provide JSON results, RSS is less likely to receive them, despite their existence.

At least for now, Astro clearly falls short in this category. Its built-in ability to provide RSS feeds is rather limited, and it doesn’t yet enable JSON feeds at all.5 In the meantime, some users, including Yours Truly, have gotten around this by using the third-party feed package, which supports RSS and JSON feeds.6

want to also support JSON Feed?

-------- # Metadata comes from _data/metadata.json permalink: "{{ metadata.jsonfeed.path | url }}" eleventyExcludeFromCollections: true -------- { "version": "https://jsonfeed.org/version/1", "title": "{{ metadata.title }}", "home_page_url": "{{ metadata.url }}", "feed_url": "{{ metadata.jsonfeed.url }}", "description": "{{ metadata.description }}", "author": { "name": "{{ metadata.author.name }}", "url": "{{ metadata.author.url }}" }, "items": [ {%- for post in collections.posts | reverse %} {%- set absolutePostUrl %}{{ post.url | url | absoluteUrl(metadata.url) }}{% endset -%} { "id": "{{ absolutePostUrl }}", "url": "{{ absolutePostUrl }}", "title": "{{ post.data.title }}", "tags": [ {%- for tag in helpers.removeCollectionTags(post.data.tags) -%} "{{tag}}" {%- if not loop.last %}, {%- endif %} {%- endfor %}], "summary": "{{ post.data.description }}", "content_html": {% if post.templateContent %}{{ post.templateContent | dump | safe }}{% else %}""{% endif %}, "date_published": "{{ post.date | rssDate }}" } {%- if not loop.last -%} , {%- endif -%} {%- endfor %} ] }

Your wish is my command.