Azure-docs: Docs out of date?

[kumlien]

Hi, seems this pages is slightly ouf of date: after step 2 (click the two paint brushes) there is no list to scroll, there are only 'Styles' and 'Templates' available.
br svante (looking for a way to edit colors for the main div with classes "container layout" btwn 'zone-content' and 'zone-navigation')

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: bc1bc76f-ca90-55f5-289c-da905f8272a4
• Version Independent ID: 648fc8c4-615f-ed0f-d6a7-62a0d3ec718e
• Content: Modify page contents in the developer portal in Azure API Management
• Content Source: articles/api-management/api-management-modify-content-layout.md
• Service: api-management
• GitHub Login: @antonba
• Microsoft Alias: antonba

[kobulloc-MSFT]

@kumlien Thank you for the feedback! We are investigating this and will get back to you shortly.

[kobulloc-MSFT]

@kumlien I'm seeing the same thing. There is only "Styles" and "Templates" available (as well as "Publish" at the bottom). I'm going to assign this to the author (@antonba) so they can update the document.

[antonba]

I no longer work on this team. Can @miaojiang who is still on that team please fix it? Thanks!

[pauliandraper]

This documentation is still wrong. Can this please be corrected?

[kobulloc-MSFT]

@pauliandraper Thank you for pointing this out. @miaojiang has this on their backlog, and will get to it as soon as they are able.

[placetobejohan]

If I'm not mistaken you still have to do this via the Publisher portal. See https://www.microsoftpressstore.com/articles/article.aspx?p=2873368&seqNum=5 -> Customize the developer portal.

[CastleArg]

In the Publish portal there is a "Widgets" section where you can change things like the main header content. I still can't find how to change the "API Documentation" and "Developer Support" text on the home page...

[eberleinm]

The content is still out of date. If you want to change widgets, menu or any other content, you need to run Publisher Portal and do your job there. No other way. In Developer Portal you can change style and layout. It helps I hope.

[mm-gmbd]

Content is still out of date, and it's very confusing because some of the content on the developer portal can be modified via the templates, but some other content can only be modified via the publisher portal.

After a little digging, it seems like the developer portal was created on top of Orchard CMS (direct link to Managing Widgets). That documentation may help to explain things a bit.

I think the following is accurate, so here's what I've learned now if you need to make changes to the developer portal:

• On every page except for the landing/home page, the content in the "middle" of the page (highlighted in red below), can be updated/modified via the templates in the Developer Portal)
  
  Although, I will say it's still not clear how to change, for example, the text "Applications" because the text itself is a template variable that is not described anywhere that I've found, much less can be changed:
  
• If you want to modify anything outside of the "Content" section, or if you want to modify the content of the home page, then you have to do so on the Publisher Portal
  
  
  
  • To modify the content of the home page, then you need to go to the "Content" section and modify the "Welcome" section
    
    
  
  
  • To modify the content of the Header or Footer, go to the Widgets section and select the header or footer widget and update the HTML there
    
    
  
  
  • To modify the contents of the navigation, go to the Navigation section and then you can add/edit/delete items. I haven't figured out how to create a "new" page. For instance, I change the text "Products" to "Subscriptions", but if I change the link from "/products" to "/subscriptions", I'm not sure how to create the "subscriptions" page.
    
    
  
  
  • Also, I haven't found out a simple way to modify the general page CSS, but there is a way around this. Choose an element that is rendered on each page (I chose the Header widget) and in the HTML you can add a <script> tag that does some CSS modification:
    
    
    
    This changes the background of the page to light-grey instead of the standard dark-grey.
  
  

This notice, which says that the Publisher Portal has been deprecated since April 1st, says the following:

Features that still need to be migrated to the Azure portal will remain available to customers until an alternative is available

I'm guessing modifying the home page/header/footer/navbar/etc all fall under "features that need to be migrated", but it would be GREAT if that was actually stated somewhere and how/what developers need to do in the meantime until it's all migrated.

Hope this helps!

[mm-gmbd]

FYI -- building on my last comment. If you need to add a new page to the developer portal, it can be done so via the "Content" section in the Publisher Portal:

[miaojiang]

please-close

Thanks for the feedback. We are planning on changes in this area and will incorporate the feedback in a future time.

[mm-gmbd]

@miaojiang @MicahMcKittrick-MSFT sorry to be a stickler, but shouldn't this be closed after whatever changes are implemented and deployed?

Seeing a "closed" ticket, to me, means that whatever issue the ticket is addressing is resolved or, in the case of it being closed as a "wontfix" then obviously it's not going to be fixed. But, this doesn't fall into either category -- it will be addressed, but it's not yet complete. For that reason, I'd opt for keeping this open until it's actually addressed for the consumers of the product.

[chenlonghu]

Hello @MicahMcKittrick-MSFT @miaojiang , no offense but I totally agree with @mm-gmbd here, this ticket shouldn't be closed since the changes are not implemented yet, or at least in the published version of the doc you should mention this issue and suggest to use the old Publisher portal instead.

[BjoernLaemmerzahl]

It is not until is was reading through these comments that I found out why I can't change parts of the developers portal in the new publisher portal. Instead I have to use the old one. Very confusing.