Format modules according to new NEBULA

[Cmurilochem]

No description provided.

[raar1]

@Cmurilochem OK so the problem was that the deployment script was configured to pull from the main branch (content_ref was set to main) which didn't contain some of your new markdown files (e.g. info.md) resulting in somewhat cryptic looking errors during pre-rendering:

[log] [nitro]   ├─ /api/_content/query/JGHrabsM16.1715865825256.json (3ms)
  │ ├── Error: [404] Document not found!
  │ └── Linked from /NEBULA-content-template/modules/module1/info

I changed the content_ref to point to github.ref which always points to the current branch you've checked out (in this case, update_module_format branch) and the workflow finishes successfully.

We can run with this for now, although we will need to make a 'dummy' deploy workflow so that this doesn't actually get pushed to gh-pages (before we've actually agreed to merge with main). I will make some modifications on the NEBULA to allow this to happen. But for now I think it's ok if you merge this or otherwise continue with what you were doing :)

[Cmurilochem]

@Cmurilochem OK so the problem was that the deployment script was configured to pull from the main branch (content_ref was set to main) which didn't contain some of your new markdown files (e.g. info.md) resulting in somewhat cryptic looking errors during pre-rendering:

[log] [nitro]   ├─ /api/_content/query/JGHrabsM16.1715865825256.json (3ms)
  │ ├── Error: [404] Document not found!
  │ └── Linked from /NEBULA-content-template/modules/module1/info

I changed the content_ref to point to github.ref which always points to the current branch you've checked out (in this case, update_module_format branch) and the workflow finishes successfully.

We can run with this for now, although we will need to make a 'dummy' deploy workflow so that this doesn't actually get pushed to gh-pages (before we've actually agreed to merge with main). I will make some modifications on the NEBULA to allow this to happen. But for now I think it's ok if you merge this or otherwise continue with what you were doing :)

Haaaaaaa @raar1. Thank you so much! So, this was the problem then 😀. Thanks for your help!