![]() Now you could manage larger sites and even hand off content editing to someone else without worrying about them breaking the rest of the site. ( Large preview)ĭreamweaver 4 introduced editable regions, which was the first foray into separating content from the layout on a static website. Table template in Dreamweaver 1.2 released 1998. ![]() At this point, dynamically generated websites had already solved this problem with includes. You would need to make that change on every page. For example, let’s say you had a website and wanted to change your navigation. Maintaining layouts became a particular pain point for static sites. The idea of drag’n’dropping website components while still having control of the HTML was groundbreaking at the time. These desktop applications incremented the tooling an inch closer to the modern Jamstack content management systems of today. Piecing together a website using a WYSIWYG editor and seeing the code it generated was a fascinating and educational experience that sparked an initial interest in web design. I vividly remember receiving a PC Magazine for my birthday with a trial of Dreamweaver. The 90sĭuring the 90s, we saw two content management systems for static sites - Microsoft FrontPage in 1996 and Macromedia Dreamweaver in 1997. In this post, we’re taking a stroll down memory lane to look at the CMSs that gave rise to the Jamstack CMSs we have today and peek beyond the horizon of what’s next. Over the years, there have been many different approaches and evolutions of static and Jamstack CMSs. Now there’s a massive range of Jamstack CMSs available, which bring all the advantages of static sites while allowing non-technical folk to update content. However, unlike the early days of the web, static sites are no longer limited to developers working in a code editor. Throughout the web’s history, static websites have always been a popular option due to their simplicity, scalability, and security. Yet, for all these technological developments, it’s interesting that many of us are still serving sites in the same way Tim did with the very first website - a web server serving static website files. Sir Tim Berners-Lee couldn’t have possibly imagined the weird and wonderful place the world wide web would become and how deeply it would become part of our everyday lives. Fast-forward 30 years, and website technology has changed significantly - we have images, stylesheets, JavaScript, streaming video, AJAX, animation, WebSockets, WebGL, rounded corners in CSS - the list goes on. While it looks unassuming, it laid the foundation for the web we have today. The world’s first website was made from static HTML files created in a text editor. In this article, we take a trip down memory lane to see how we got to the modern Jamstack CMSs we have today, and where they’re heading in the next decade. The story of Jamstack CMSs goes all the way back to the 90s.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |