Ability to decommission old web content templatesAbility to decommission old web content templateshttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1184142602024-03-29T10:10:59Z2024-03-29T10:10:59ZRE: Ability to decommission old web content templatesDavid H Nebingerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184251092020-02-04T23:56:27Z2020-02-04T23:56:27ZI think you missed the spirit of my ask, how do you envision marking templates as "deprecated", unmarking them, and menu handling across the board? I mean, if we seriously want to turn this into a proposal, well let's spec it all out so there's no ambiguity in it.<br /><br />Web content is not going away, who said it was? We can show widgets (portlets) on content pages, so you have a choice between web content and page fragment.<br /><br />I can't see doing every article that we have now as a page fragment. In the same way that web contents alone aren't solutions for every use case, neither are page fragments.David H Nebinger2020-02-04T23:56:27ZRE: Ability to decommission old web content templatesLee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184216272020-02-04T15:44:29Z2020-02-04T15:44:29ZA status flag would be the desired solution yes, keep it in the system but have it prevented from being used going forward by site admins. Right now I do a dangerous CSS play on the main menu where users add new content. Hide everything, show a whitelist of menu item names.<br /><br />Workflows need to be there out of the box. Sure you get some teams and implementations that are on it and can set stuff up, but on workflows there's nothing there out of the box for someone to base a learning experience on. Then Approved / Unapproved could work, I doubt if the logic in the code is setup right now to hide these flagged templates.<br /><br />So in terms of Web Content going forward, is that going away? Pump the brakes on that swap it over to that? Because honestly I don't know what the future of content in Liferay is at this point.<br /><a href="https://www.youtube.com/watch?v=8lZeTTXyIk4">https://www.youtube.com/watch?v=8lZeTTXyIk4</a>Lee Jordan2020-02-04T15:44:29ZRE: Ability to decommission old web content templatesDavid H Nebingerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184152882020-02-04T01:35:28Z2020-02-04T01:35:28ZHmm, interesting...<br /><br />So I know how you could find a template in a list in order to set some kind of "deprecated" flag...<br /><br />But how do you envision finding these in order to change them back? Or does the list in web content templates include the deprecated ones but mark them as deprecated in the list or something?<br /><br />Also, in any UI where you need to select a template, would you want to see some kind of checkbox to "include deprecated templates" or is it like, if they are deprecated, you are simply not allowed to pick them at all?<br /><br />I mean, at first blush I kind of see this as maybe a new workflow state, DEPRECATED. That would leave them around but, since they're not APPROVED, they would not normally be used in some kind of selection. But based upon your answer on the checkbox thing, well that makes things get a teensy bit more complicated...David H Nebinger2020-02-04T01:35:28ZAbility to decommission old web content templatesLee Jordanhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1184142592020-02-03T22:22:56Z2020-02-03T22:22:56ZNeed ability to hide old web content templates from menus. Not delete old templates but when there is a template we don't want a user to use anymore our solution at the moment is to remove all menu items and re-show a white list of items. We then append the templates we do want people to use as Global - from global templates and Local - for locally scoped templates.<br /><br />This then gives us the ability to stop the very valuable + menu from being overcrowded. There was a solution that DXP UX had to this to favorite web content templates and also search templates from this menu ... whatever happened to that item of gold star improvements? These are the small things that make a big difference.<br /><br />ul.dropdown-menu a[id*="_com_liferay_journal_content_web_portlet_"] {<br /> display : none !important;<br />}<br /><br />ul.dropdown-menu a[id*="menu__homesite_2d_"],<br />ul.dropdown-menu a[id*="menu__local_2d_"],<br />ul.dropdown-menu a[id*="menu__global_2d_"],<br />ul.dropdown-menu a[id*="menu__basic_2d_web_2d_content"],<br />ul.dropdown-menu a[id*="menu__advanced_2d_web_2d_content"],<br />ul.dropdown-menu a[id*="menu__html_2d_content"],<br />ul.dropdown-menu a[id*="menu__test_2d_"],<br />ul.dropdown-menu a[id*="menu__lexicon_2d_"],<br />ul.dropdown-menu a[id*="menu__clay_2d_"],<br />ul.dropdown-menu a[id*="menu__material_2d_"],<br />ul.dropdown-menu a[id*="menu__flat_2d_"],<br />ul.dropdown-menu a[id*="menu__look_2d_and_2d_feel_"],<br />ul.dropdown-menu a[id*="menu__export_2d__2f__2d_import"],<br />ul.dropdown-menu a[id*="menu__configuration"],<br />ul.dropdown-menu a[id*="menu__permissions"],<br />ul.dropdown-menu a[id*="menu__subscribe"],<br />ul.dropdown-menu a[id*="menu__unsubscribe"],<br />ul.dropdown-menu a[id*="menu__configuration_2d_templates"],<br />ul.dropdown-menu a[id*="menu__remove"],<br />ul.