Clear questions and runnable code
get the best and fastest answer
Perl & Templating for a mobile future.by punch_card_don (Curate)
|on Jan 15, 2013 at 19:42 UTC||Need Help??|
punch_card_don has asked for the
wisdom of the Perl Monks concerning the following question:
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?
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.