HTML Exports from EA on Sharepoint

[maarten58]

Hi,

There are already several posts on this subject, but I can't get an HTML export (generated from EA16) that I placed in a SharePoint folder to be displayed properly in a browser.
When I navigate in my browser to the map containing the index.htm and open the index.htm by clicking on it, then the start page doesn't display properly. And when I click on a package then I get the message that the file is not found.

When I synchronise the map or add a shortcut to OneDrive, and from that map open the index.htm, the start page is displayed properly and I can navigate through the model.
I want to share just the sharepoint link, and I don't want that users have to synchronise the SharePoint map.

I am not an SharePoint expert, so can anyone tell me how I can get an HTML export of an EA model displayed properly and navigable in SharePoint?

Thanks,
Maarten

[Sunshine]

If you search "static html on sharepoint" you'll find some posts on the topic. https://sharepoint.stackexchange.com/questions/162019/is-there-a-way-to-host-static-html-using-office-365-sharepoint

To host static HTML content in SharePoint, you'll need to rename your HTML files to .aspx and adjust the links accordingly. Then, you can upload these files, along with any necessary assets like CSS and JavaScript, into a document library within your SharePoint site. Finally, set the desired page as the site's homepage if needed.

Here's a more detailed breakdown:
1. Rename HTML files to ASPX:
For single-page websites, simply rename the .html file to .aspx.
For multi-page websites, rename all .html files to .aspx and update all internal links within the site to reflect the new file extensions.
2. Prepare your site assets:
If your HTML site uses CSS, JavaScript, or images, ensure these files are also uploaded to the appropriate folders within your SharePoint site.
For example, you might create a folder called "Assets" or "Images" within your document library and upload these files there.
Update the paths in your HTML files to point to the correct locations of these assets within your SharePoint site.
3. Upload files to SharePoint:
Navigate to your SharePoint site and access the document library where you want to store your website files.
You can use the default "Shared Documents" library or create a custom one.
Upload the folder containing your .aspx files and other assets.
You can upload files directly or create a folder for your website content and then upload all the files into that folder.
4. Set the homepage (if needed):
If you want a specific page to be the default homepage for your site, select it in the document library, click the three dots (more options), and choose "Set as home page".
5. Addressing DenyAddAndCustomizePages setting:
Modern SharePoint sites have a setting called DenyAddAndCustomizePages which can prevent the site from rendering HTML files correctly.
If you encounter issues, you might need to temporarily disable this setting using PowerShell.
To do this, you'll need to connect to your SharePoint site using the SharePoint Online PowerShell module and then use the Set-SPOsite cmdlet to disable this setting.
Important: After making your changes or publishing new content, you may want to re-enable the DenyAddAndCustomizePages setting for security reasons.
Example:
Let's say you have a simple index.html file. You would:
Rename it to index.aspx.
Create a folder in your SharePoint document library (e.g., "MyStaticSite").
Upload index.aspx to this folder.
Navigate to the index.aspx file in your browser.
If it works, you're done. If not, you may need to adjust the DenyAddAndCustomizePages setting using PowerShell.
Note:
This method is suitable for hosting static HTML content. It is not designed for dynamic websites that rely on server-side logic.
If you have a more complex site with multiple dependencies, ensure you have all the necessary files and that the links are correctly configured within your HTML files.
If you encounter issues with rendering HTML files, check the DenyAddAndCustomizePages setting and adjust it if necessary.

NOTE: The above was all generate by Google AI when I did the search.

Or you could purchase Prolaborate and use the built in integration with Sharepoint.https://prolaborate.sparxsystems.com/resources/v5-documentation/enterprise-architect-model-and-sharepoint-integration