Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Mellifluous Monks,

Been gone a while, but back with a green-field website development project:

desktop website design providing future mobile delivery groundwork preparation

We are to define the design framework for a new website from the ground up for delivery on desktops - which currently accounts for 90% of users. But, knowing that mobile users will increase, we want to lay the groundwork for mobile delivery not too far away. That is, design the desktop version so that a mobile version can be built later without havng to start from scratch again.

What's this got to do with Perl?

Our favourite framework is for dynamic websites. LAMP stack, and Template Toolkit. So our first instinct is to strip out content into separate files with semantic markup or a database, detect the browser or device, and dynamically serve the content in a custom template with appropriate css and javascript.


Then you get all caught up in Graceful Degradation and Progressive Enhancement and Responsive Web Design.....and suddenly the place of server-side page assembly seems in doubt. And yet - as an old server-side coder - I find myself suspecting that the reliability of server-side dynamic generation, while not "hip" or sexy anymore, is still our friend.

Note that I am talking about what might be called a "document site" - that is, not a web application - just information delivery. And lots of it - so a fairly complex and deep navigation structure.

So, if there's a question in there, I guess it's: Has Perl, or server-side processing in general, responded to the emerging mobile delivery question? Has browser or device detection through headers become any more reliable than it used to be? Is there a place for such approaches in a RWD world?


Time flies like an arrow. Fruit flies like a banana.

In reply to Perl & Templating for a mobile future. by punch_card_don

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (5)
    As of 2019-02-16 21:58 GMT
    Find Nodes?
      Voting Booth?
      I use postfix dereferencing ...

      Results (95 votes). Check out past polls.