Things I discovered in Beta still needed

[thominator (Thom Hogan)]

Okay, I’ve been quiet as I promised I would be, but as beta gets further and further along there are few things I’ve discovered using it that need addressing.

1. When you create a new page, it creates and selects a new page, but you can’t immediately type a new name for it. If you try that, you end up in search. You have to click again (in the name itself, not the selection) to rename that new page. It’s NEVER going to be titled Untitled Page, so just take us to typing the name upon creation.
2. We need a way to edit Globals. As the site gets more and more complex and you’ve been using globals to create you, you then find that you needed to change something in the global that all your pages are using. Yes, I could create a new global, but then I have to apply it to every darned page I created, and I’m prolific ;~).
3. We need short versus long menu names (could be defined in the page inspector where menu description is). Why? Because as sites get more complex, multiline menu names start to be a problem and need abbreviating to take up less screen space. On the desktop on want to use longer menu names (more descriptive) and need them to be wider, while in the mobile hamburger, I’ll end up with scrolling menus if I use long names.

[dan (Dan C.)]

@thominator

When you create a new page, it creates and selects a new page, but you can’t immediately type a new name for it. If you try that, you end up in search. You have to click again (in the name itself, not the selection) to rename that new page. It’s NEVER going to be titled Untitled Page, so just take us to typing the name upon creation.

To make your workflow smoother, try this, press: “Command-N”, then “Enter”.

Enter/Return will edit the page title, you can also use the arrow keys to navigate up and down the tree…

@thominator

We need a way to edit Globals. As the site gets more and more complex and you’ve been using globals to create you, you then find that you needed to change something in the global that all your pages are using. Yes, I could create a new global, but then I have to apply it to every darned page I created, and I’m prolific ;~).

Globals are editable (always have been), just drop (or remove) a new component into them and boom it just works…

@thominator

We need short versus long menu names (could be defined in the page inspector where menu description is). Why? Because as sites get more complex, multiline menu names start to be a problem and need abbreviating to take up less screen space. On the desktop on want to use longer menu names (more descriptive) and need them to be wider, while in the mobile hamburger, I’ll end up with scrolling menus if I use long names.

Interesting feedback, we’ll definatley think about this one. Although, it sounds like it might be a great component for a third party to build…

[handshaper (Robin Mair)]

@thominator

• We need a way to edit Globals. As the site gets more and more complex and you’ve been using globals to create you, you then find that you needed to change something in the global that all your pages are using. Yes, I could create a new global, but then I have to apply it to every darned page I created, and I’m prolific ;~).

This already works great and is one of the beauties of a global. Anywhere you are already using the global if it needs a change just apply the change and it magically will update every place that is using that global. It is a godsend and I rely on it all the time.