Here’s the proposed way of dealing with new pages in Cristal. There are two scenarios that I worked with. One of them is more Notion like, meaning there’s very little friction when creating a new page and another one that’s more in line with what’s implemented right now.
To make things simpler to explain I did this proposal as a interactvie prototype so you can get a better feel for the experience (and I can save some written paragraphs explaining every single detail ).
Note that I mention the selection of templates on both, but they are not part of the mockups right now. I plan to expand on this further.
What happens in option 1 when selecting a template?
Does the user get a startup content?
Is the user able to switch to another template if they realize it’s not what they expected?
I’m asking because it seems to be the main difference between the two options.
Furthermore, it’s not so clear to me how the page location choice is done in option 1.
I don’t see older discussions and proposals being mentioned.
Can you check how they overlap each other?
I also think this proposal is missing an analysis of how the design choices are applicable to XWiki.
It goes to the template selection page, I didn’t create it yet though because I wanted to get something out to start discussing earlier.
The way XS works is that these templates already offers some type of content together with the layout. I think the behavior should be the same in Cristal, of course this means producing said content.
Once the template is selected, no, I don’t think so, as two templates might have completely different content. We can however:
Quick previews for each template before selection;
Have an option to “Reset” or “Clear” the current page, which deletes the selected template content and then the user can select another one. This option should be temporary though, available only right after template selection, we don’t want to induce the user to erase custom content.
Ah yes, I didn’t mention it, my bad. The default location would be as a child of the current page. For this, the button besides the breadcrumb makes more sense.
In the past I was thinking that the button on the sidebar should create the pages on the root (or as a child of “home”) but I think having two behaviors for the same action might be more confusing than it’s worth.
Will do
Option 2 is closer to the way XWiki works right now, but with a different layout. But the process is the same:
User selects Create
Fill in Name, location and template
Page is created.
I can however check how would Option 1 work for XWiki. For this, I’ll also check the two proposals that you linked above.
Sounds good as the default, but it might be interesting to have an action somewhere to move the page, the same way as what’s proposed for the template.
Though if moving pages is easy enough, it might not be useful.
).