3 ms·
I think the future may be CMS-style applications that do static publishing. Either run locally (may be a great use for electron actually), and/or as a service.
by tracker1 10y ago
I think the future may be CMS-style applications that do static publishing. Either run locally (may be a great use for electron actually), and/or as a service. At least in this space competitively, the biggest complaints tend to center around the amount of manual configuration/changes... opposed to the overhead of say wordpress.
The only downside to static publishing to say S3/ABS is that you loose server-side analytics to some extent.
- mxuribe 10y agoBut then, couldn't you insert the google analytics javascript snippet within the html that gets loaded/served up from S3? Or did you mean something like piwik? I have to think S3 would not be a block here, as many users of static site generators also use some sort of analytics tool.
- tracker1 10y agoThere are bits that JS based tooling will miss in terms of a bigger picture... they don't represent your real load when you run a site that is getting hit by a lot of different smaller search bots. Of course, once you're on s3 or a similarly cheap static delivery option (and/or CDN), you may not actually care.
- wodenokoto 10y agoDreamweaver seems kind of relevant again with the resurgence of static site generators. It had (has?) powerful wysiwyg for both developing site layout and mechanics as well as for writing content and can publish content to server.