Camp create: choose prototype UX improvement

[manuelmeister]

With this PR I want to improve a part of the camp creation process. This PR concerns the initial camp creation sent to the api.

To explain that you actually select a template with certain predefined categories, states and layout templates, I've move the prototype selection to a secondary screen.

On the template screen (prototype seleciton), I've created a screen that warns the user if they select "No template" and shows the predefined content that comes with a certain template.

Future possibilities

Category Description

Currently I display the preferredContentTypes, but eventually I think it would make more sense to make it an editable description in a following PR.

Prototype per URL

Maybe we could also provide the entry "from url" in the prototype selection, this way, local groups can share their prototype easily. This own screen would suit this idea very well.

[github-actions]

⛔ Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.

[manuelmeister]

Core Meeting Decision

• We think this is a reasonable suggestion. It would also make way for an eventual camp copy ability. (Select item "URL", then field appears to input the camp prototype url and then we can apply it as a template)

• We want an alert to prevent users from choosing the no-template.

• The description is a good idea we want to pursue further

[pmattmann]

I like it very much! 😊

A problem:

• The "Back" button on the second wizard page does not work.

Questions:

• On the second wizard page, there is a preview for the categories and activity status. Is this self-explanatory enough? Or do we need a small text?
• The wizard shows 3 nodes - but there are only 2 pages. I was surprised that after the second page I have already created a camp.

[BacLuc]

You need to merge devel again after #4136

[manuelmeister]

@pmattmann I thought the step 3 might help to imply that you need to configure the categories. But in this case I'll remove it for the moment. This will be fixed by the camp configuration (not creation) wizard.

On the second wizard page, there is a preview for the categories and activity status. Is this self-explanatory enough? Or do we need a small text?

I don't understand your point. What kind of small text would you envision? What does it explain?

[pmattmann]

@pmattmann I thought the step 3 might help to imply that you need to configure the categories. But in this case I'll remove it for the moment. This will be fixed by the camp configuration (not creation) wizard.

On the second wizard page, there is a preview for the categories and activity status. Is this self-explanatory enough? Or do we need a small text?

I don't understand your point. What kind of small text would you envision? What does it explain?

The two sections "Activity category preview" and "Activity states preview" are the same width as the "Camp Prototype"-selector. It therefore conveys that they are independent elements. And therefore also that you can / should do something there.

Counter-suggestion:
A kind of sub-element (Card in Card?) so that it is better expressed that it is only informative detailed information on the selected "Camp Prototype". Possibly even a text à la: "Camp prototype Y+S contains the following categories:"