What is the point of the index.html file in the acul boilerplate?

There is an index.html file in the acul boilerplate project, but I cannot find an example with the endpoint to set a screen’s render settings in which an html file is sent. What is the point of it?

It looks like that needs to be sent over in the Set render settings endpoint, otherwise I’m left with a blank page referencing my static assets.

I found a doc article stating that there is no root div element in the tag because some front-end frameworks prefer to create this div in the “initialization step”.

What is the “initialization step”? It’s not referenced anywhere else in the article. What about front-end frameworks that don’t do use this step? I’m using React and I don’t believe it does.

@BrandenRobinson the purpose of the index.html file is to allow for developing a screen locally without needing to be connected to an Auth0 tenant. Initially this was the spot where develoers could manually insert mock context data (tenant/transaction data) to build out static versions of the screens. In the latest version of the sample app, we have streamlined this workflow and provided a better way to define and load mock data when building a static version of the screen locally.