depends on the goal: if the passion is to learn some new tech then well, there are lots of options, i'd pick something that i haven't worked with yet. if it i

depends on the goal: if the passion is to learn some new tech then well, there are lots of options, i'd pick something that i haven't worked with yet. if it is something where the passion is in the content, i would use the same old stack that i used for my last few projects. in my case that is aurelia+custom backend which is a reusable object storage and user management platform, where i didn't need to add any project specific features for some time now. if i could not use that backend, i would pick something that makes it easy to manage objects through a REST API. if i had to evaluate a new framework then the main thing that i would look for is the ability to minimize or avoid any dependency on build tools. unfortunately, with the rapid evolution in frontend frameworks there is also a rapid evolution in build tools. that just adds extra effort to maintain a site for more than a few years. without buildtools getting in the way i can maintain a site with minimal effort, and i know it will still be running in a decade from now.