SallyMcGrath
commented
11 months ago content reorganisation... all headless blocks as a module? Yes. I'd like to move the blocks out of the modules. There is already a top level blocks folder just for headless blocks (that do not create their own pages).
Blocks maybe should exist separately from the organisation of those blocks. We had them in the module because one giant blob of blocks would be hard to manage, so i'm proposing moving them like this:
from
content/databases/blocks/*
to
content/blocks/datatabases/*
it's totally fine to move the blocks around -- the platform doesn't require they live in the module dir - that's a legacy from an older, suckier pattern in the early days
Which module(s) and week(s) does this change affect? Module(s): n/a Week(s): n/a
What is the work that needs to be done?
We need to structure a parent and child module system that creates a common core with two children, equal siblings: CYF and MigraCode
Why is this work important to do?
We are making our curriculum available to be codeveloped with MigraCode and also assuming other orgs are joining next year.
Additional context
More context to come when this ticket is refined.
-- for local development, we use a replacement line https://gohugo.io/hugo-modules/configuration/#module-configuration-top-level
We need to store this in the .env I think, and have something clever in the command line that echos the path to our env or else we will create a trapdoor
Who might need to know about this change?