Madeline

@Racer159 - I agree that more validation is needed. I am working off of the assumption that we can use the UI to get feedback from users from different skill...

@JasonvanBrackel Any thoughts on a way to organize these packages? @YrrepNoj Is there a way to automate their generation for each release?

This feature would help with usability testing as well. It would allow me to have users to download all packages needed from the github page without me asking a dev...

@jeff-mccoy Yes the init package is already published each release and there is a way using the install to pull the already built package using brew, however, this would allow...

@jeff-mccoy This is a different flow from the connected quick install zarf.dev/install - where we would want to user to download the package. We still have the quick install though.

@jeff-mccoy Yes. How those files are accessed, published or organized is up to the team.

@jeff-mccoy I looked at the docs and agree. Here is my assessment of what could be contributed to this error. - walkthroughs are not segmented by user role or skill...

@Racer159 - I agree that more validation is needed. I am working off of the assumption that we can use the UI to get feedback from users from different skill...

> Specifically: > > ``` > variables: > - name: "NOTHING" > - name: "NO_PROMPT" > default: "no-prompt" > - name: "NO_DEFAULT" > prompt: true > - name: "BOTH" >...

@RothAndrew This is helpful. I think to get the feedback we are looking for having common or easily understood examples will be helpful. The users I have discussed variables with...