After learning how to authenticate users on a Remix app with Discourse, I couldn’t resist trying to display Discourse topics in the app.
Tag: remix
DiscourseConnect Authentication for Remix
This is a proof of concept. It might lead to something interesting.
Contextual Navigation (take two)
The goal is to give the site’s users a sense of where they are without overloading them with details.
Toggle Open/Collapse On Click
Looking into displaying posts in a child route of a category archive parent route, the first thing that comes to mind is that the archive’s posts listing on the parent route needs to expand/collapse on click.
Route configuration
The goal of this project was to display the text “Hello World!” at https://hello.zalgorithm.com. It somehow morphed into creating a Remix client application that consumes a headless WordPress site. I’ve been working without much of a plan. That’s starting to show in the application’s URL structure.
Using the previousPost and nextPost Fields
Yesterday I made a WPGraphQL Adjacent Posts plugin. It adds fields that can be used for obtaining adjacent posts to the WPGraphQL Post type schema. I’m going to use those fields to add previous/next navigation to the Remix app.
Featured posts
With pagiation out of the way, it’s time to clean up the home page. Instead of displaying the 5 most recent posts at the top of the page, it’s going to pull in the site’s “featured” posts. I’ll mark posts as featured by giving them a “featured” tag.
Pagination (take five: success!)
I realized the problem I’m having with pagination is that I’m trying to implement page based pagination but WPGraphQL has been optimized for cursor based pagination.
Pagination (take four)
Why do this at all if LLMs can write adequate code and blog posts? The short answer is that they can’t, yet. The longer answer follows from LLM’s lack of understanding and common sense.
Pagination (take three)
Yesterday I added pagination to the app’s Archive route with the useFetcher hook and the fetcher.Form component. This works, but using forms to create navigation elements feels weird. It also adds some complexity to the code: