video1.0<iframe src="https://www.loom.com/embed/e0e8866450d54c52b161e77907d1ccb9" frameborder="0" width="1114" height="835" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>8351114Loomhttps://www.loom.com8351114https://cdn.loom.com/sessions/thumbnails/e0e8866450d54c52b161e77907d1ccb9-00001.gif293.63Hey there! In this Loom, I want to give you a better understanding of the folder structure and rendering of our app. Currently, we have two ways of rendering the app, which causes a bit of jank when loading. We have a lot of files that restructure data and compute likes, which are then packed into HTML and delivered. Only the interactive parts of the page are reactive components, which are inserted into the page separately. We use a separate app called source web source to insert these components. If you're working on the front end, you'll need to go to main.js to insert these components. We render the page on the server for SEO purposes and caching. We want to avoid vendor lock-in and make it easy for everyone to work on the code. In the future, we hope to move towards using web components to render the app. If you have any questions or need help, please don't hesitate to reach out to me or others in the dev chat.