Paul Hettler

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.

In the current Portals frontend editor, it is possible to click an 'Insert Template' tool, and add a Web Template. We have developed several of these web templates for our content editors to use - for things such as Call to Actions, Accordions, and much more.

In the new Power Pages, where the Page Template uses an include I can see a reference to 'Custom Component' - but there is no way to edit that, or insert other Custom Components into the page.

Could you please add an 'Insert Component' tool, which would act like the 'Insert Template' tool on the Portals front-end, and add a Web Template into the page?

Crucial to this working well, would be the ability to switch to code / html view for the component, as many have text that need to be edited, eg a Call to action.

This feature is as important as ever with the new addition of conflict detection and merge features from VSCode for the web. 

https://powerpages.microsoft.com/en-us/blog/configuring-code-components-properties-from-the-design-studio-now-available-in-public-preview/

As the intention of Web templates as components | Microsoft Learn seems to be to allow makers to reuse these components easily - one glaring omission is that Design Studio lacks the ability to add custom components (Web Templates with manifests).

Seems like it would be an easy win to add a section for Web Templates and allow developers to open in VS Code.

The conflict resolution would be great to have. 

Additional thoughts on how to make working with Web templates better.

1. In web templates section have 2 or 3 collapsible groupings 
2. Components - Items with a manifest
3. Page Templates- Templates that are related to a page template
4. Other
5. Alternatively (since a Template may be a page template and have a manifest) Just having some sort of visual indicator for if manifest is present/is related to a page template
6. Add a GUI for working with manifest of a web template. Options in the '...' 
7. View Manifest - Show a pop up with manifest details so users know what templates inputs are and can read description
8. Edit Manifest - Would be nice to have a low code way of authoring manifest so user error is reduced
9. Create Component - If the web template was not a Component open editor to add component definition 
10. Selecting a web template in '...' Create Component then allow editing the manifest with low code tools. 
11. Add way to add a template as a component in the same menu as adding 'text', 'image', 'video','button', etc. 
12. Preferably multistep process where select "Component" then a listing of components including details from manifest I am thinking something similar to when you pick a PCF control on a model driven app. (Actually adding a thumbnail to web templates would be a cool concept too for the content editors to see perhaps a preview of what they are getting) 

Credit to Eric Sutter who posted this idea 9 months ago in Power Pages Idea forum - which doesn't seem to be used by Microsoft's product team.

When editing using the Design Studio it only allows editing in the default language. 

In sites with multiple languages designed to use many snippets for localization content editors must use the Portal Management app to edit snippets out of context from the pages they occur on. 

It would be beneficial to be able to toggle the language of the portal in the designer to allow a preview of the content in said language and the ability to edit page copy and snippets in place. 

I don't know how Design Studio was released without the ability to choose the editing language.

Credit to Eric Sutter who first posted this 9 months ago in Power Pages Ideas Forum, which seems Microsoft does not monitor.

Our makers 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 makers' 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 PowerPages Design Studio.

As the frontend content editor has been deprecated, this is a very high priority for our organization. Thank you for your consideration.

It is surprising that we don't have the ability to edit any SEO fields whatsoever from Design Studio. Title and description should be the bare minimum. Other SEO fields like og:image should also be supported and easily editable on the page settings popup.

It should not be required to switch to Portal Management app to do things such as:

• Change the Page Template
• Set page's Publish status, or Access Control
• Edit SEO fields (title, description, image, etc)
• Edit the page's custom CSS / JS

These should be accessible from the Page's Settings field (which currently only shows name and partial URL).

Currently, Power Pages Design Studio auto-saves changes to the live website, publishing changes live that are not yet ready! It should not function this way - but should have a clear Save / Publish distinction. Save would store the changes temporarily but not publish, while Publish would make them live.

Design Studio also does not allow you to view version history, track changes and revert to previous versions. This would be a fantastic improvement on a system edited by multiple makers.

While the new image component in Design Studio allows for a simple upload process, there is no corresponding upload feature for any other file type eg PDF. Previously, in the Frontend editor, you could click on the ckeditor link button to add a file to the system. Sadly, this means the DS is less capable than your previous product.

Our users are often adding PDF files to download. Currently, there is no way to do this in Design Studio. Please address this. Perhaps the image uploader could be modified so it can handle both images and files?

Both the file selector and image selector should allow for search (by name or partialurl), or filtering by parent page. It is currently very hard to find the correct file in a site with hundreds of images/files. Please add a search filter to the image / file browser.

The Image component in Design Studio allows users to choose an existing image from the website, and shows images by thumbnail, which is an improvement on the previous system.

However, all the images on the site are listed in one long block. While the user can select the page to upload images to using Advanced Tools, it does not allow filtering based on that parent page. Nor is it possible to search images by name or partial url.

We have sites with hundreds of images - please add a search filter that allows searching by name, partial url, and parent page.