Skip to content
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

Closed
16 tasks done
wezell opened this issue Jun 2, 2022 · 3 comments
Closed
16 tasks done

New Favorites Pages Portlet #22343

wezell opened this issue Jun 2, 2022 · 3 comments

Comments

@wezell
Copy link
Contributor

wezell commented Jun 2, 2022

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 and device that has been selected for viewing. Additionally, we should take a screenshot of the page at the time of the save using something like html2canvas, 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 a

  • title,

  • 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

  1. OKR : Core Features QA : Approved QA : Passed Internal Release : 23.06 Team : Lunik
    rjvelazco zJaaal
  2. Merged QA : Approved QA : Passed Internal Release : 23.05 Team : Scout
  3. OKR : Core Features Release : 23.06 Team : Lunik Type : Enhancement dotCMS : Admin Tools
  4. OKR : Core Features QA : Approved Release : 23.06 Team : Lunik
    alfredo-dotcms
  5. Merged QA : Approved QA : Passed Internal Release : 23.05 Team : Scout Type : Enhancement dotCMS : Admin Tools
    jgambarios
  6. Note to QA QA : Approved QA : Passed Internal Release : 23.03 Team : Scout Type : Enhancement dotCMS : Admin Tools
    josemejias07
  7. QA : Approved QA : Passed Internal Release : 23.03 Team : Scout Type : Enhancement dotCMS : Admin Tools
  8. Merged Note to QA QA : Approved QA : Passed Internal Release : 23.03 Team : Scout
  9. QA : Approved QA : Passed Internal Release : 23.03 Team : Scout Type : Defect
    josemejias07
  10. Merged QA : Approved QA : Passed Internal Release : 23.05 Team : Scout Type : New Functionality dotCMS : Admin Tools
  11. Merged OKR : Core Features QA : Approved QA : Passed Internal Release : 23.06 Team : Lunik Type : Defect
    alfredo-dotcms
  12. Merged OKR : Core Features Priority : 4 Low QA : Not Needed QA : Passed Internal Release : 23.06 Team : Lunik Type : Defect
    alfredo-dotcms jdotcms
    jgambarios
  13. Merged OKR : Core Features QA : Approved QA : Passed Internal Release : 23.06 Team : Lunik Type : Enhancement dotCMS : Admin Tools
  14. Merged OKR : Core Features QA : Approved QA : Passed Internal Release : 23.06 Team : Lunik dotCMS : Admin Tools
    rjvelazco
  15. Merged QA : Approved QA : Passed Internal Release : 23.05 Team : Scout
    jgambarios
  16. QA : Approved Release : 23.06 Team : Lunik Type : Defect
    fmontes rjvelazco
@wezell
Copy link
Contributor Author

wezell commented Jun 2, 2022

@stale
Copy link

stale bot commented Jan 2, 2023

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.

@stale stale bot added the stale label Jan 2, 2023
@github-actions
Copy link

github-actions bot commented Feb 2, 2023

This issue was closed because it has been stalled with no activity.

@fmontes fmontes changed the title New Favorites Interface New Favorites Pages Portlet Apr 17, 2023
@fmontes fmontes closed this as completed Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

5 participants