-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Favorites Pages Portlet #22343
Labels
Comments
wezell
added
Epic
Team : Scout
dotCMS : Admin Tools
and removed
dotCMS : Admin Tools
labels
Jun 6, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue was closed because it has been stalled with no activity. |
damen-dotcms
added
dotCMS : Admin Tools
Type : New Functionality
Epic
and removed
stale
labels
Feb 22, 2023
damen-dotcms
changed the title
Channel Manager - Site Entry point
New Favorites Interface
Feb 22, 2023
This was referenced Apr 5, 2023
This was referenced Apr 17, 2023
fmontes
added
OKR : Core Features
Owned by Will
Next Release
Release : 23.06
and removed
Next Release
labels
Apr 18, 2023
This was referenced Apr 20, 2023
This was referenced May 3, 2023
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Problem:
With all the improvements in edit mode, managing pages in dotCMS should be easy. But forcing content editors to dig through dotCMS’s file browser to find the right “index” page and then having to double click on it can be daunting for non technical editors. We need to get rid of the "index file" experience.
Content editors need a quick way to pop open a site or subpage in edit mode, and use the site to browse to the page they want to edit and get busy. And it would be nice if content editors could bookmark pages for quick, 1 click access to manage them.
Solution: Start Pages & Favorites
We need to create a portlet that shows a user card views of “start pages”. A “Start Page” is just a saved url for a page that can be clicked on and the user be instantly taken to the given page in edit mode, including the selections for device, persona and language that were set when the start page was created.
(Internal doc)
https://docs.google.com/document/d/1yRX50V5rbFE3u1BEtOAnTcH9VjuQSDepljlpYDSm3sA/edit
Figma Wireframe (still in development) :
https://www.figma.com/file/aL0kTopu5OJ96S166GRyxC/Channel-%2F-Page-Manager
Portlet Card View (Default View)
The cards should be shown in alphabetical order.
Adding a Start Page
From edit mode, start pages can be added by any user for themselves. If a start page is added by a CMS_Admin, they can choose to share it with one or more roles.
When saving an edit mode view as a start page, we should the whole page url with the page’s parameters like
host_id
,language
,persona
anddevice
that has been selected for viewing. Additionally, we should take a screenshot of the page at the time of the save using something likehtml2canvas
, save it as a dotAsset and show this screenshot when displaying the card.If the page is being viewed as a device, the screenshot should be taken using the width/height that is set in the device.
Start pages can be added by users for themselves and/or by admins to share with users. In card view, should these lists of start pages (“my start pages” and “shared with me”) be shown together or should they be separated visually?
Removing a Start Page
If a user has added a start page for themselves, they can click on a pencil box on the card's top right corner and edit or delete it (after confirmation) - normal users can only remove start pages they have added themselves. If the user is a CMS_ADMIN, they can click on the pencil of a shared start page card and delete them from everyone’s view.
dotStartPage Content Type
To persist start pages we should create a system content type called
dotStartPage
. This type would consist of atitle,
a binary field for the screencap
a url (textarea)
an sortOrder integer field that will be used to sort the start pages.
We will need an upgrade task that creates the dotStartPage content type on startup. The dotStartPage content type should be marked as a “system” content type.
Sub-tasks
Tasks
The text was updated successfully, but these errors were encountered: