In Rapidweaver you can name a Page whatever you want, as it’s just a place holder. You can then go into settings and give a page title and path. Why doesn’t Blocs work like this? In blocs the page name get’s automatically inserted to the end of the path. Becuase of this I have to put the actual url that the page will have even if it’s a long url. This make it very hard to identify pages when your in pages view. Is there a way around this or is this just the way Blocs handles it.
2 Likes
This is really almost a deal breaker for me using Blocs on this project. I have over 40 pages like this I’m inheiriting from the previous builder. I don’t know which page is which unless I click on the page to view it. The only work around I can see is creating a folder for every location page and naming the folder so I know what page it is. @Norm is there a better approach to this that I’m missing?
1 Like
I started organizing the pages with Folders, it’s actually working better than I thought it would, I think it will work. It still would be nice to have the page name as just a place holder, but the folders are a decent compromsie.
2 Likes
Hey, as you mentioned Blocs uses the page name you set in page settings for the file name and the reference in the Page Navigator.
This is how Blocs has always worked with regards to page naming. Over the years the page and URL features of Blocs have been expanded to include custom paths and browser title.
The reason why Blocs is set up to use the page name in the page navigator and as the file name, is to lower confusion and keep things as simple as possible. Having multiple names for a page could be confusing, especially when you also have browser title as well (Page Name, File Name, Browser Title), making it 3 separate names for a single page.
I’ve noted down your feedback as a possible expansion in the future. Thanks for your feedback.
2 Likes