4

Our content editors spend more time editing BlogPosts on our Portals websites - for news, articles, etc, than WebPages. Currently, PowerPages only allows for editing WebPages.


The Portal Management content editor is very poor for user-friendliness. Our content editors' jobs would be much easier if everything to do with editing the website's content could be in one place.


It would be ideal if you could add the ability to create and edit BlogPost entities from the make.powerapps.com portals editor, or PowerPages editor.


We have also added custom fields to WebPages and BlogPosts, mainly for SEO (Tags, description, OG Image, OG Video, etc). In Portal Management we have custom forms to edit these fields. It is far from ideal to have to use 2 different editing tools to update the same piece of content.


Could you add a way to make these fields editable from within the new editors, like PowerPages? For example, when editing a WebPage, the content editor could click a 'Page Settings' link, that would open up a form (which could be managed in Solutions as is already the case).


As the frontend content editor is set to be deprecated and removed later this year, this is a very high priority for our organization. Thank you for your consideration.

STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. Currently this is not on our roadmap, but we are tracking it, and with more feedback and support from the community we may consider it in the future. Sincerely, Petr Jantac, Microsoft