- Is it better to build on a separate subdomain or on the same domain?
- Is it better to build an admin panel from scratch, or download from a library? Most I've seen don't work without JavaScript.
This is based on the type of project generally. For instance a blog or tiny directory might not require as much security as a marketplace. So i think it should be proportionally to the project. If it's just a blog, you can just put the admin panel on the same domain, maybe use role based view and still apply general security practices. As for building the admin panel since you want no js i'm guessing you wanna build a dn site so the best route is to build from scratch or carefully re-construct one from a downloaded library if your project allows it.
So you consider js to be insecure for an admin panel? If so, why? I have a few next.js sites live with the admin panel in the same domain and with js and this post made me worry.
absolutely not. I don't consider JS to be insecure for dashboards. But if you intend to manage a website anonymously, js is incompatible with the mode of use you intend.
Can you briefly describe what of js make it not anonymous? What should we use instead if we want anonymity, pure HTML?
Use backend maybe (?) I'm saying that the administrator who intends to stay anonymous also made a web application carefully and didn't put javascript, or put just a little. Therefore, the admin himself will also make a panel without javascript. In the same way he designed the application. It's just an example