Unfortunately its not well implemented with the Portal. One other thing you need to consider is if it is just readonly or do you need someone to edit it on the Portal? (the reason why this is important is that you cannot save HTML tags back to dataverse from the portal, unless you set a global setting that turns off some of the field validation - and if you do this you then need to create your own plugin code to perform such validation)
If it is just readonly:
The portal has 'filters' that are applied that tell it how to render the various elements, using the standard Entity Form etc you do not have access to these filters, but you can apply them in a custom web template. If the page is just readonly - then building a custom web template, with fetchxml and placing fields may be an answer. If it needs to be editable, you can now use the Web Api to update etc (still a custom web template, fetchxml etc but you can add your own submit button etc).