Feature ideas

In the specific entity, add the ability to change the order of the properties that displayed in the "Details" section on the "Overview" tab

At the moment, when we create a md, swagger or proto we also have a tab in the entity page. We would like this ability also for Json properties

a specific entity view can become extremely cumbersome when it holds many properties (whether it's own, mirrored, calc) and relations. more over, different personas viewing an entity would probably have interest in different properties. we think it would be great if properties can be added to a "label" when designing in the Data Model which would explain to what "groupping" the property belongs to. On the entity view, the labels can be either "tabbed" or folded in an accordion view.

Currently, when searching for related entities, all related entities in the blueprint specified will be returned. This feature will allow for the specification of the relation path, allowing different visualizations to be based on it. For example, Create separate tables for 2 types of relations to the same entity.

Currently, you can ingest markdown documents into Port by creating markdown properties. Each document will be displayed in Port as a tab on the specific entity page. We would like to add the ability to create a "documentation tree" for each entity, allowing you to create a full wiki inside your developer portal. Similar to the singular markdown documents, the documents in the "documentation tree" will be searchable via the global search .

Right now choosing an Object/Json for a blueprint property is less than ideal because it literally displays as json to the user. However, this is not a great experience for the end user because Json is not nice to look at and some users might not understand it. Current implementation is shown in the picture with the red arrow below. My suggestion is to create a better method of displaying object/json inputs to the user as maybe a popup if they click into the object. Such as the below image about user details. Maybe some nicer method of displaying key/value pairs when you click into the object on the entity screen.

Ask questions, discuss, and make decisions within context. Allow developers to discuss and comment on different entities directly in Port.

New design for the specific entity page to improve the ease of navigation The specific entity page will have an “overview” dashboard section. It will be fully customizable (like global dashboards), letting you choose the structure, widgets, etc. In addition, you will be able to add multiple dashboards to the specific entity page.

Currently, Port offers a standardized view and set of filters on entity pages that all users must adapt to. While this uniformity ensures consistency, it does not account for the diverse needs and workflows of individual developers. Developers often require quick access to specific information or prefer to interact with data in a way that aligns with their personal workflow or the unique demands of their projects.

As part of the OAS standard you can reference parts of the specification to either other files using a relative path or URL https://swagger.io/specification/#reference-object It is very common practise to do this with shared schemas across specifications in Enterprise organizations. There are tools that can combine specs into a single file, would be great if Port can handle this automatically