templates and lists of aggregated content meant setting up complex content management systems. These CMSs consisted of templating logic, application code, and content databases so they could assemble webpages each time they were requested by site visitors. They were complicated systems that depend on many separate applications working together, like a web server to route page requests to a PHP application that uses pre-defined page layout templates to format content that’s stored in a MySQL database. Serving a page request required at least three separate applications all working together — any one failing would bring down the system…
Engine to multi-million dollar proprietary applications that the government and big corporations procure from companies that also build tanks and battle ships, these systems produce the same exact output: HTML, CSS, and JavaScript files that web browsers know how to format into the webpages we see. Additional features like RSS or JSON API feeds are just new templates for the same content, and backend workflow modules like those for embedded media and handling email notifications are really separate systems that introduce complexity when integrated with the publishing system.
benbalter
knih
z63d
%20zoom.jpeg){kind=avatar}
avosalmon
tarotaro0129
rssytems
iidaxs
yuj1osm
shingo_kawahara
oniak3ibm
drumnistnakano
tsukuha
nagisa53
garrettdimon
paulrobertlloyd
mongodb
bcantrill
marktimemedia
bkeepers
jponch
maggiecrowley
gr2m
thoeni
jonyablonski
