Stop Publishing web Pages
dashes.com
Stop Publishing web Pages
1–10 of 16 posts
Re: Stop Publishing web Pages
#2The OP took a reasonable idea: stop shoehorning content systems into producing static HTML pages (and instead, produce an API)...and jumps somewhat illogically to "make it all a stream!"
Why isn't it possible to create an API which you dogfood to produce static pages (because permalinks are nice) AND content for streams?
Re: Stop Publishing web Pages
#3[deleted]
Re: Stop Publishing web Pages
#4[deleted]
Re: Stop Publishing web Pages
#5This post seems a little naive. yes, people spend a lot of time on things like Facebook, Twitter, Google+ etc. However, that's only half the story. People also use search engines to find information. Information that is organised in pages, e.g. Wikipedia or Amazon. Streams are fluid. Information is there and gone the next. Pages and streams serve two different purposes and one does not exclude the other.
Re: Stop Publishing web Pages
#6It's interesting that in a "blog about making culture" that he doesn't address the issue of archival. While a CMS can produce a nice snapshot for archive.org or another mirror to capture, streams are trickier, especially if they rely on the app that produced the stream(s) to work.
Re: Stop Publishing web Pages
#7It's interesting that in a "blog about making culture" that he doesn't address the issue of archival. While a CMS can produce a nice snapshot for archive.org or another mirror to capture, streams are trickier, especially if they rely on the app that produced the stream(s) to work.
Wouldn't streams actually make it easier? The site that wanted to do the archiving could subscribe to the stream and slurp up the content as it became available. As far as crawling older content presumably having a stream doesn't preclude you from also having permalinks to each entry.
Re: Stop Publishing web Pages
#8I'm actually kind of tired of sites that just give a stream of data.
That's why on all my projects going forward, I'm going to try to take the next step and design the page itself to be attractive as to the placement of the content---more like a magazine, than like a Reddit.
Re: Stop Publishing web Pages
#9Streams are not always the best solution. How do you get an item at the end of the stream? By scrolling for minutes and hoping your browser doesn't crash...
It's a model very well-suited to social publishing, immediate content, not so for articles/timeless information.
Re: Stop Publishing web Pages
#10Streams are not always the best solution. How do you get an item at the end of the stream? By scrolling for minutes and hoping your browser doesn't crash... It's a model very well-suited to social publishing, immediate content, not so for articles/timeless information.
the browser crashing problem just shows it's still such a new paradigm that programmers still are not tackling the problem correctly. many libraries are already being written to better handle this problem.