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.
+1 for prototype 1, as it allows creating content faster, and that the fact the page is located under the previous page is logical (and not a problem if the page can then be moved, by drag&drop in the navigation for example)
We could also add the template selection possibility in the page content, displaying a tooltip to preview what the template looks like. Thinkinh this could also allow us to propose creation of a LD, an AWM, a Task manager kanban, etc.
I agree that it’s a useful feature. Note that on option 2, the preview could be useful too
IMO temporary buttons that disappear on abstract technical conditions should be avoided, we need to make it very clear why this button appears/disappears. I think the first idea is easier to do well from a UX point of view.
Overall, prototype 1 looks good. Thank you for the explanation about picking location
Having it easy enough to move I think it’s more important, when creating a page we want the user to focus on content right away instead of where to put it. Thinking about it makes me wonder if it’d be useful to have a “recent pages” on the profile page or somewhere else that’s easily accessible. It would be for these cases in which someone created/edited some page but forgot or was interrupted.
I’m just thinking what the behavior should be if the user already has something in the content. We could:
1- Warn the user about it and, upon confirmation, overwrite all content (I’m not a fan of this route, unless reverting to the old content is really really easy)
2- Add the content before or after the written content.
3- Add the content exactly at the point the cursor is, this means that the template selection could be a slash command menu. I guess for smaller pieces of content it could work well. But for full templates this could mean too much added content.
4- ? I’m not really sure but perhaps someone have a better idea.
Ah, then I guess I misunderstood, what do you mean. In your reply, you wrote “We could also add the template selection possibility in the page content, displaying a tooltip to preview what the template looks like.” My understanding is that we would have the template selection available at all times in the page (with content or not).
).
