For a Future-Friendly Web

by Brad Frost

16 Reader Comments

Back to the Article
  1. @timkaplor
    You’re absolutely right that we need better ways of determining context. This falls in line with the “Unknown Vessel: Identify”: section of Future Friendly thinking.

    There’s definitely been talk about using the server to serve up more contextually-aware experiences:
    “Adaptation: Why responsive design actually begins on the server”:,
    RESS, Server-Side Feature-Detection and the Evolution of Responsive Web Design”:
    RESS: Responsive Design + Server Side Components”:

    It’s becoming more of an issue, especially with things like the new iPad screen. As Jason Grigsby recently pointed out, will unfortunately “serve up multiple images”: to users, mostly because there’s no way for the server to know that the device has a hi-res screen right out of the gate.

    In order for us to deal with this huge amount of diversity, we need to be able to fire on all cylinders. I think we’ve got a long way to go to get to what you’re describing, but at the same time we need to keep pushing to make more sense of it all.

    Copy & paste the code below to embed this comment.
  2. @himedlooff

    Any CMS recommendations that offer clean content storing?

    This is a really good question, and I wish I had a short list of well-defined solutions to give you. I think that ultimately it comes down to using the tools in the right way and considering the right things when implementing a CMS.

    Keep your eyes on karenmcgrane, lyzadanger, and @jensimmons as they talk a lot about CMSes as they relate to future friendly thinking. In the meantime, I’ll see what I can do to find out more resources and insight.

    Copy & paste the code below to embed this comment.
  3. Very nice article. Indeed relevant data is the key….Google is going even forward to the future creating the new Google Glasses with 3d holographic hud that will make your ads full targeted and 24/7….facebook is also on the same road…you can find info about “φαψεβοοκ”:http://www.xn— here

    Copy & paste the code below to embed this comment.
  4. Hi good morning,

    We are a web design <a href=“”> </ a> in Barcelona, Madrid and wanted to thank you for the article as we serve for the next fururo and congratulate them on that note that is actually doing people fully qualified in this sector.

    Thank you very much,


    Copy & paste the code below to embed this comment.
  5. I think we (as an industry) need to embrace the “content like water” concept, and realize that content strategy, user experience, layout, design, and development are more tightly integrated than ever before. It is difficult for many to accept this loss of control – over how the page appears, and how the users are accessing the content and the pages.

    We need to be adaptable to whatever comes next, and willing to learn new ways of going through our process.

    Thanks Brad, for this insightful article, and the myriad of resources you put out there for the web industry.

    Copy & paste the code below to embed this comment.
  6. Thanks, Brad. The Create Once Publish Everywhere method only makes sense when dealing with vehicles like website, app, etc., but does this methodology work for things like parent company site to child company site? Would this result in redundant content?

    Copy & paste the code below to embed this comment.