Skip to content

Conversation

@joelostblom
Copy link
Contributor

@joelostblom joelostblom commented Nov 7, 2025

Description

This is an attempt to elaborate and clarify what is needed to get started with creating a data package and manage its package-level metadata. There are more motivation behind the individual changes in the commit descriptions. It's a larger PR, but since the changes are related for these two doc pages, I thought it made sense to keep it as one instead of splitting it up.

Closes #1573 closes #1575 closes #1576 closes #1115

Needs an in-depth review.

Checklist

  • Formatted Markdown
  • Ran just run-all

Adding additional sections and trying to explain more clearly what each step does
Draws more attention to it without interupting the flow
I'm unsure if we should use the `important` callout everywhere
or try to use `note` more, so that not everything is marked as `important`
Setting `output: asis` makes quarto try to render the printed text as markdown.
I think this makes it much easier to see what is important in the script
and looks less intimidating than a raw print outupt.
This will later be moved to another page in the guide
…te test

I'm not sure if there was additional utility in the metadata in the separate file, but I
think it mages sense to test with the same metadata in the guide to make sure that it
works
And remind people never to edit this file manually
Breaking these up into two sections makes it less overwhelming at first glance.
Just to make it clearer what I change in the following commits
To point out some of the things more explicitly to the reader.
@lwjohnst86 lwjohnst86 moved this from Todo to In Review in Iteration planning Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment