[x] “Facilitate model-free characterization” – what does it mean to be model-free?
[x] Make_design could also work where you repeat values in the vector
[x] Landing page is wall of text feeling, and I’m giving context for why it can do somethings, so I can cut that down a lot. Limit each bullet to 2 lines so it’s less intimidating
[x] “also facilitates several strategies to deal with” – is so wordy
[x] “downstream” is a technical term, cut it just “for analyses”
[x] Maybe a layman’s version on the landing page “gcplyr was created to make it easier to x”
[x] Landing page just a lot less intimidating
[x] Design vignette is super long. Noah just wants a basic feeling of how to do the basics then move on to merging. It took super long to get to merging.
[x] Design “advanced notes” can go somewhere else
[x] It’s almost like I’ve been too thorough with the notes/text
[x] Not all the functionalities have to be explained in the articles
[x] Can cut down some of the repetitiveness “That’s right! It imports a block-shaped and outputs a tidy-shaped”
[x] “programmatically” is jargon, just say directly in R
[x] “If you find it easier to input the pattern as a vector rather than as a string that needs to be split, you can do that too. Just like when passing a string, if you’re not using numbers, then uppercase letters, then lowercase letters for your indices, make sure to specify a different lookup_tbl_start:” Noah got confused about what the string was referring to (that it was the previous sections where it wasn’t a vector)