@demwunz
not enough lines.
front end dev.
Nothing here yet.
No blogs yet.
was it ever relevant? The term was taken from print design and production at a time when the web was still fairly new and the only way to access it was through a desktop device. Most screen sizes were fairly similar and you could predict fairly well what something would look like. Nevertheless, it was still an arbitrary term that allowed designers and content managers to sell shit into their stakeholders and clients. Now we can access the web through a plethora of devices with a multitude of screen sizes and resolutions, "the fold" is even more defunct then when the silly term first arised. Design for your user and their needs, not for a technical constraint you may never encounter.
None of these choices lean towards creating a CMS. This isn't the correct way to approach this problem. Understand the difference between Page based CMS's and Node based CMS's. This will fundamentally effect the direction you take your project: look at your core concerns address those before you commit to working with the above frameworks. does it need a database? can it be static? Like any framework, choose one that suits your ideas, your project the best. Make sure the community and support are what you expect and what you can engage with. Until then I would consider looking at the following JS based CMS's: keystone webhook apostrophe