Edit to recipe.md

@bsnodgrass - We talked yesterday and I was in agreement with you here, that we should remove this line. However, I am reviewing this now and I think deleting this line may not be the correct action. I think this is attempting to clarify that creating content is in scope for recipes (the content will only be created in the database on the environment the recipe is applied to), but recipes are not responsible for deploying that created content to a secondary environment and/or recreating the content on those other environments.

In other words, in a standard workflow, you may apply a recipe on your local environment, test changes, export configuration and deploy to dev, stage, live, etc. Recipes will create content on the local environment, however when you deploy changes to those additional environments, e.g. dev, stage, live, etc, Recipes will not create that content on those additional environments.

If that is the case, and content creation is a requirement of recipes; then the recipe would have to be re-run on each environment.

While I do think it would be helpful to have content created as part of a recipe deployment, the Roadmap specifically states this in not within scope.

Do we want creation or updating of content specific to a recipe? If so we should update the Roadmap and close this issue was "won't fix"

Since the parent issue is still active, it seems this one should be postponed until that decision is finalized. I think we should leave the debate and how to address default content on the parent issue.

Content is content, and while there are ways to deploy content, there is nothing in core, or being proposed in recipes that would deploy content.

If the content a recipe is providing is needed on a different environment, the recipe would need to run on that environment.

Maybe we could update the doc to include the above to add additional clarification.

Recipes can now deploy content. Closing this.

Automatically closed - issue fixed for 2 weeks with no activity.