This project is read-only.

Is it by design to display a page after editing, but not creating?

Topics: General
Jul 6, 2011 at 8:14 PM
Edited Jul 6, 2011 at 9:00 PM

I'm writing a tutorial on creating and editing pages - a users first experience with orchard in their first few minutes with the product:

It's based of this:

My version is here (temporarily):

In my version I don't want the user to immediately select the page to be added to the main menu. I want them to do it at a later step, so they experience the win/simplicity of checking a box and having control over the menu. But if it's not selected then they can't even browse to it on the font-end. The way I have to suggest to them to get it to is to go to "Content" and hit "View"... this isn't the worst, but I'm still think they should be able to click a button/link - from the edit page to get to it.

Or... be taken straight to it like the edit flow? I'm curious as to why they are different.

Jul 6, 2011 at 11:08 PM

I'm having trouble following what you're saying here, and the post seems to be down.