resource query (resource migration 1/3) by interim17 · Pull Request #71 · AllenCell/idea-board

interim17 · 2026-03-11T02:34:13Z

Problem

Advances #40

Line count inflated by formatting stuff. Next priority needs to be getting those pre commit checks up and running so we can iron that out.

Next PR in series is here: #72

Solution

We have created a single resource collection in the CMS. Now we need to consume these resources.

The primary goals of this PR are to successfully convert those resource markdown files into useful gatsby nodes, build the pages associated with resources, and query the resource nodes wherever they are needed.

gatsby improvements and upgrades come along for the ride.

Resource Nodes

Up until now, all our nodes in our gatsby data layer were of type MarkdownRemark. This has pros and cons. In this PR we create a type Resource that implements Node

This resource type is flat, relative to MarkdownRemark, in that it does not have frontmatter or fields but only top level properties.
It is also flat relative the resource .md files in that it does not have a nested ResourceDetails field, but only top level properties.

It can be queried with allResource and resource which is a nice option to have.

These nodes are created explicitly in onCreateNode. The MarkdownRemark nodes are created, mysteriously, by a plugin.

Resolvers

Resolvers can take direct advantage of these nodes, we should have done this before. See the resources resolver for a nice pattern using context.nodeModel.findOne(resourceQuery(name)) This typing and way of handling the resolver replaces the @link directive in a way that is more pleasant.

onCreateNode and createPages

We make resource nodes and resource pages in a way that is extendable to other forthcoming types. We map over TEMPLATE_KEY_TO_TYPE. This wasn't strictly necessary for this PR but it's good practice and I know another use is right around the corner. When we want to make an Allenite node or page, or a Program node or page, it will be set up.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…eature/resource

…into feature/resource

…board into feature/resource-query

…eature/resource

…board into feature/resource-query

…eature/resource-query

into feature/resource-query

netlify · 2026-03-11T02:34:18Z

✅ Deploy Preview for project-idea-board ready!

Name	Link
🔨 Latest commit	`1a233ec`
🔍 Latest deploy log	https://app.netlify.com/projects/project-idea-board/deploys/69bc0c59c48c66000891bde2
😎 Deploy Preview	https://deploy-preview-71--project-idea-board.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

interim17 · 2026-03-11T05:48:08Z

gatsby-node.js

+            resources: {
+                resolve: async (source, _args, context) => {
+                    const names = resolveToArray(source.resources);
+                    const results = await Promise.all(
+                        names.map((name) =>
+                            context.nodeModel.findOne(resourceQuery(name)),
+                        ),
+                    );
+                    results.forEach((result, i) => {
+                        if (!result) {
+                            const msg = `Resource "${names[i]}" not found for idea "${source.title}". Check for typos and ensure the resource file exists with the correct templateKey.`;
+                            reporter.error(msg, new Error(msg));
+                        }
+                    });
+                    return results.filter(Boolean);
+                },
+            },


A different way to handle the resolution, using context.nodeModel.findOne, where before we would use a @link directive in the schema. Both are valid ways of doing things. I think I prefer this way because we get a bit more color, as in the example of doing error handling with the reporter.
https://www.gatsbyjs.com/docs/reference/graphql-data-layer/node-model/#findOne

Do we really need error handling here? We have some now.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…/idea-board into feature/resource-query

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…/idea-board into feature/resource-query

Copilot

Pull request overview

Copilot reviewed 28 out of 28 changed files in this pull request and generated 4 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

gatsby/schema/base.gql

    materialsAndMethods: MaterialsAndMethods!
-    authors: [String!]!
-    nextSteps: [String!]
+    authors: [String!]


gatsby/utils/test/gatsby-resolver-utils.test.js

gatsby-node.js

+                        names.map((name) =>
+                            context.nodeModel.findOne(resourceQuery(name)),
+                        ),


…eature/resource-query

interim17 · 2026-03-11T15:16:36Z

src/pages/resource/index.tsx

+import * as React from "react";
+import { Helmet } from "react-helmet-async";
+
+import { Link, PageProps, graphql } from "gatsby";
+
+const ResourcesPage: React.FC<PageProps<Queries.ResourcesIndexQueryQuery>> = ({
+    data,
+}) => {
+    const { allResource, site } = data;
+
+    if (!allResource || !site) {
+        return <p>Data not found.</p>;
+    }
+
+    const { nodes } = allResource;
+    const title = site.siteMetadata?.title || "Title";
+    return (
+        <section>
+            <Helmet title={`Resources | ${title}`} />
+            <div>
+                <h1>Resources</h1>
+                <ul>
+                    {nodes.map((node) => (
+                        <li key={node.slug}>
+                            <Link to={node.slug}>{node.name}</Link>
+                            {node.description && <p>{node.description}</p>}
+                            {node.type && <p>{node.type}</p>}
+                        </li>
+                    ))}
+                </ul>
+            </div>
+        </section>
+    );
+};
+
+export default ResourcesPage;
+
+export const resourcePageQuery = graphql`
+    query ResourcesIndexQuery {
+        site {
+            siteMetadata {
+                title
+            }
+        }
+        allResource {
+            nodes {
+                slug
+                ...ResourceFields
+            }
+        }


Mostly a proof of concept, just showing in all the relevant places that the new data and approach is working.

meganrm · 2026-03-16T17:47:51Z

src/pages/ideas/dev-example.md

    (rapid local changes in junction length and intensity) increases ~30–60
-    minutes before migration onset in a subset of fields of view. Here is a link for no reason: [link](https://allencell.org/).
+    minutes before migration onset in a subset of fields of view. Here is a link
+    for no reason: [link](https://allencell.org/).


frasercl

I will have to make a point to learn a bit more about Gatsby! I left a couple basic clarifying questions about the style and architecture, at least one of which is bound to be dumb, but this is looking good as far as I can tell.

frasercl · 2026-03-18T22:20:35Z

gatsby-node.js

+const {
+    DATASET_PATH,
+    RESOURCES_GATSBY_NODE_KEY,
+    MARKDOWN_REMARK_GATSBY_NODE_KEY,
+    TEMPLATE_KEY_TO_TYPE,
+} = require("./gatsby/constants");


Another optional clarifying question: any rhyme or reason to what gets CommonJS-style vs ESM-style imports? I guess these and the files in gatsby/ are either config or server-side...?

Historical anachronism from gatsby's age and the template this repo was started from.

I think webpack handles src and gatsby-browser.js and Node directly handles the other gatsby configuration files. I think we would need to migrate everything at once and it's just been low on my list, but it is starting to get annoying. Maybe I should do that next. Gatsby supports ESM now, it didn't always.

https://www.gatsbyjs.com/docs/how-to/custom-configuration/es-modules/

frasercl · 2026-03-18T22:24:47Z

src/types/index.ts

    IdeaFrontmatter["preliminaryFindings"]
 >["figures"][number];

+export type ResourceTemplateQuery = Queries.ResourcesByIdQuery;


Large block comment above is very helpful for understanding why this works despite the red squiggle TS throws up on Queries

Yes... Curious if it smells bad to you to be defining types downstream of the generated types.

In cell-catalog we wrote types based on what we expected the queries to give back which gave rise to some interesting bugs. This way is a little annoying, but it keeps the data layer and the front end in tighter lock step.

frasercl · 2026-03-18T22:34:18Z

src/pages/resource/index.tsx

+
+import { Link, PageProps, graphql } from "gatsby";
+
+const ResourcesPage: React.FC<PageProps<Queries.ResourcesIndexQueryQuery>> = ({


Seeing some query types with Query at the end in the graphql declaration, resulting in this QueryQuery name in TS, and some without. Any reason for some to be one vs. the other?

Mmm just style, I think before we were using the generated types we had a pattern of putting query at the end of the name, and now should probably be moving away from that since it produces the redundancy.

frasercl · 2026-03-18T22:40:53Z

src/pages/tags/index.js

Out of curiosity: any reason this file is a plain .js file?

We initialized this repo from a template, we are migrating away from their style over time, but some things are in the old style which included a lot of plain JS.

I'm tackling patterns like this as I hit them, to avoid massive, unreviewable refactors.

…eature/resource-query

interim17 and others added 29 commits February 19, 2026 14:23

register custom widget for variable type resources

37fd2cf

use resourceDetails in nested fields on resource markdown

5e1c540

query new resources collection

75fbc17

Update src/cms/widgets/VariableResourceWidget/copyResourceNameHandler.ts

9f43b2b

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update static/admin/config.yml

a345633

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

reference resourceDetails in relational widget

478c946

Merge branch 'main' of https://github.com/AllenCell/idea-board into f…

e0fd5b2

…eature/resource

remove redundant fields from config

cc336ee

fix typo

6653ea5

run format

eb6b692

Merge branch 'run-format' of https://github.com/AllenCell/idea-board …

3e89540

…into feature/resource

update comment

211c55a

Merge branch 'feature/resource' of https://github.com/AllenCell/idea-…

ee27bd4

…board into feature/resource-query

add resources to schema

00d073e

add pages for resources

2bdcb98

format resource template

879d577

add ResourceDetailsField fragment

1a50470

build resource pages separately from MarkdownRemark

1e1ee25

Merge branch 'main' of https://github.com/AllenCell/idea-board into f…

079639a

…eature/resource

format and lint

f9283a8

Merge branch 'feature/resource' of https://github.com/AllenCell/idea-…

be3ef5c

…board into feature/resource-query

import resources path

971039c

add a resources index page and a second dev example tool

c12a1aa

make programs an array and next steps a markdown string

72038d2

Merge branch 'main' of https://github.com/AllenCell/idea-board into f…

fc2b31f

…eature/resource-query

Merge branch 'fix/next-steps' of https://github.com/AllenCell/idea-board

f793be6

into feature/resource-query

fix duplicated fields in dev-example

89d19e2

flatten resource details when building gatsby nodes

a517a79

fix typos

666a21a

update tests to cover resourceQuery

0c37800

interim17 commented Mar 11, 2026

View reviewed changes

interim17 and others added 8 commits March 10, 2026 22:50

Update gatsby-node.js

8d88a8d

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

remove tags fields from createPages calls

8264972

Merge branch 'feature/resource-query' of https://github.com/AllenCell…

0d4765e

…/idea-board into feature/resource-query

Update gatsby/utils/gatsby-resolver-utils.js

2b14e68

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Update gatsby/schema/base.gql

2c25a81

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

update comments

2127cba

remove extra layout

8411c40

Merge branch 'feature/resource-query' of https://github.com/AllenCell…

8d3b7b9

…/idea-board into feature/resource-query

interim17 requested a review from Copilot March 11, 2026 06:34

Copilot started reviewing on behalf of interim17 March 11, 2026 06:34 View session

Copilot AI reviewed Mar 11, 2026

View reviewed changes

interim17 changed the title ~~Feature/resource query~~ resource query (resource migration 1/3) Mar 11, 2026

interim17 added 2 commits March 11, 2026 08:07

fix authors schema typing

fbe2502

Merge branch 'main' of https://github.com/AllenCell/idea-board into f…

23a5c69

…eature/resource-query

interim17 marked this pull request as ready for review March 11, 2026 15:13

interim17 commented Mar 11, 2026

View reviewed changes

interim17 requested review from frasercl, jessicasyu and meganrm March 11, 2026 15:17

interim17 changed the title ~~resource query (resource migration 1/3)~~ resource query (resource migration 1/2) Mar 11, 2026

interim17 changed the title ~~resource query (resource migration 1/2)~~ resource query (resource migration 1/3) Mar 11, 2026

meganrm approved these changes Mar 16, 2026

View reviewed changes

interim17 requested a review from rugeli March 18, 2026 21:31

frasercl approved these changes Mar 18, 2026

View reviewed changes

frasercl reviewed Mar 18, 2026

View reviewed changes

Merge branch 'main' of https://github.com/AllenCell/idea-board into f…

1a233ec

…eature/resource-query

interim17 merged commit e33bdec into main Mar 19, 2026
5 checks passed

interim17 deleted the feature/resource-query branch March 19, 2026 15:38


		import { Link, PageProps, graphql } from "gatsby";

		const ResourcesPage: React.FC<PageProps<Queries.ResourcesIndexQueryQuery>> = ({

Conversation

interim17 commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Solution

Resource Nodes

Resolvers

onCreateNode and createPages

Uh oh!

netlify bot commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for project-idea-board ready!

Uh oh!

interim17 Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

This comment was marked as resolved.

Uh oh!

Uh oh!

This comment was marked as outdated.

Uh oh!

interim17 Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

meganrm Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

frasercl left a comment

Choose a reason for hiding this comment

Uh oh!

frasercl Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

interim17 Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

frasercl Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

interim17 Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

frasercl Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

interim17 Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

frasercl Mar 18, 2026

Choose a reason for hiding this comment

Uh oh!

interim17 Mar 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

interim17 commented Mar 11, 2026 •

edited

Loading

netlify bot commented Mar 11, 2026 •

edited

Loading

interim17 Mar 11, 2026 •

edited

Loading

interim17 Mar 11, 2026 •

edited

Loading

frasercl Mar 18, 2026 •

edited

Loading

interim17 Mar 18, 2026 •

edited

Loading