New API Management developer portal
We are working on a new, open-source developer portal offering in Azure API Management, based on our own fork of the Paperbits framework (paperbits.io). It has a modern default look and feel, and is optimized for:
Customization, styling, and authoring through a built-in visual editor
Programmatic access through APIs for automating development, management, and deployment
Extension of the provided core functionality
The new developer portal was released in November 2019.
Dean May commented
Would be nice to have a migration path from the old format to the new, or even be able to take the old and self host it: we have clients who would like to use API Management for the developer portal, but can't see putting the time and resources into setting up on the current production version in Orchard CMS only to have to redo any customization work when the new one is released as production.
please make the API widget also editable or change the style more like
e.g at the moment I have not found any chance to group by given tags
Doralee Moynihan commented
Please make sure ALL customized content can be stored/retrieved via GIT. I want to add my own HTML pages, etc. to a dev portal, and want everything to be source controlled and stored in GIT.
Hi,Is is possible in the new developer portal that user can view APIs/ documentation etc only after signing in ?
Peter Anania commented
I don't know whether this is a legitimate feature request, or if it's just a lack on knowledge on my behalf, so I apologize in advance if I ask for something that already exists.
Right now you can add a widget to the whole portal or edit a template for an individual screen. The data model for each screen is unique to that screen.
I need to be able to either, add widgets to individual screens only or access the data models in other screens.
The issue I'm trying to solve is (as an example) I want to be able to customize the the API list based on whether or not the logged in user is internal or external.
Nishanth Prabhakaran commented
Yes, the preview will be released on 12 June 2019
Philip Driessen commented
We are about to change to different hosting because this is still not available.
ILYA BELKIN commented
Can you please include a language toggle along with the capability to edit translations for navigation labels/emails? In Canada having English and French translation is often a requirement.
ILYA BELKIN commented
Can you please also include a language toggle along with the capability to edit translations? In Canada having English and French translation is often a requirement.
Jeroen de Sitter commented
Is it possible to get an update with regards to this feature?
Alexander Deane commented
This topic is old and no one posted an answer for some reason. If anyone still wants to know, you can accomplish this by uploading your favicon image to the publisher portal media library and putting this JS script in any one of your widgets (I put it in header since it persists for all of my pages):
var link = document.createElement('link');
link.type = 'image/x-icon';
link.rel = 'shortcut icon';
link.href = '<put url to img that can be found by clicking on your favicon img in media library, right clicking the link -> copy link address ';
Paul Appasamy commented
It would be very helpful if the Console/Try It screen has a template similar to Operations. We would like to i) mask any internal URLs that show up on this screen, ii) possibly hide the host name section altogether and, iii) force a specific URL to be used (when there are multiple custom domains)
Rick Mook commented
Definitely need this - it's a major blocker for our org.
Really need this feature.
really need that
I have noted down the Subscription key and i can give to external users to enter manually. So i need to hide this section in Developer portal operation console page
More customisability in elements such as:
- buttons - border-radius, box-shadow property
- layout - fill/stretch screen
- defined/customized link colors for different divs
Glen Colby commented
Can this get any love? We want our documentation behind a login due to business rules and cannot do something as simple as set up viewing rules based on role?
Would be great to have the option of applying the layer rules for authenticated and not authenticated users (as for widgets) also to the home page (with default api portal url) or other pages which are defined in the 'Content' section.
I've raised this to the API management team in regards to turning off the Issues feature. As discussed with them, the issue feature's upload function can pose as a security risk. They are looking into introducing a feature such as this at this moment for anyone who share this problem.