Hi @ar4s! Thanks for working on this. I was looking through the code and attempting to understand the changes, I have a few questions.

• How do the context processors work? Is this just inserting the same context values into every rendered page?
• What are these lines doing? I don't see them called anywhere on any templates. I believe this is causing an error on the page: Uncaught TypeError: window.__CONFIG__ is undefined. Additionally, why is it better to access this file via a view instead of the {% static %} tag?

I've also not used the django templating much, and think that that your method of using different blocks and base.html is a good idea, thanks for implementing that.

I made a few formatting changes (I'm a stubborn 4 tabs for indents user lol) and the alpine.js collapse plugin needs to be imported second, so I rearranged a few things in base.html and editor.html to fix this.

How do the context processors work? Is this just inserting the same context values into every rendered page?

Yes, exactly so you don't need repeat same chunks of code over and over again in views.

What are these lines doing? I don't see them called anywhere on any templates.

It is exposed in urls.py

I believe this is causing an error on the page: Uncaught TypeError: window.CONFIG is undefined.

My bad - I fixed that in c12f4a0

why is it better to access this file via a view instead of the {% static %} tag?

In this case I want to generate JS file on the fly to provide some dynamic information to present how you can pass information from backend to frontend. You can use also JSON or JSONP but i think for that scale it is enough and straightforward.
Keep in mind that you can also cache this view on different levels (app, www server, client cache).

I made a few formatting changes (I'm a stubborn 4 tabs for indents user lol) and the alpine.js collapse plugin needs to be imported second, so I rearranged a few things in base.html and editor.html to fix this.

I appreciate that because I am new in the project and I don't know how to test properly whole application.

Yes, exactly so you don't need repeat same chunks of code over and over again in views.

Got it, thank you for answering my questions

In this case I want to generate JS file on the fly to provide some dynamic information to present how you can pass information from backend to frontend

That makes sense, it's a good new method I've not used before, I'll have to keep that in mind for future

I appreciate that because I am new in the project and I don't know how to test properly whole application.

I have instructions in the README for installing it locally for development, did those steps not work for you?

In any case this issue has now been completed, I'll get it all merged, thank you!

I have instructions in the README for installing it locally for development, did those steps not work for you?

Installation is straigtforward because it is a simple Django project :)
By I don't know how to test properly whole application I meant I don't know full list of use cases and features in terms of bussiness.