{"id":22727,"date":"2016-06-15T03:01:20","date_gmt":"2016-06-14T17:01:20","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=22727"},"modified":"2016-06-16T10:14:03","modified_gmt":"2016-06-16T00:14:03","slug":"landing-page-cut-to-the-chase-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/landing-page-cut-to-the-chase-primer-tutorial\/","title":{"rendered":"Landing Page Cut to the Chase Primer Tutorial"},"content":{"rendered":"
\"Landing<\/a>

Landing Page Cut to the Chase Primer Tutorial<\/p><\/div>\n

A lot of people learning programming are trying to get information quickly, and “move on”, shall we say. While this is all well and good, it might be a “fob job” to think that many of us will really learn something well enough for the challenging bits adopting this approach, but there’s no doubt there are pressures these days to learn more and more, and perhaps come back to things in detail at a later, quieter, date. Anyway, “to cut to the chase” … chortle, chortle … this is what today’s blog post is about!<\/p>\n

Let me explain it this way. Our tutorial blog postings here at RJM Programming always involve a bit of, but not too much, we hope …<\/p>\n

    \n
  1. the background to an issue … that is always preceded by …<\/li>\n
  2. an image or slideshow or web application or game etcetera that is “the cut to the chase” part of the blog posting clickable off an image up the top of it (for all but the earliest postings we ever did) … and for those who get it through a feed (that can summarize the blog posting with words only, perhaps) …<\/li>\n
  3. if we can remember we also always have a link within the blurb of 1 that links to “the cut to the chase” that is 2<\/li>\n<\/ol>\n

    … and so what you end up with, if you want to objectify it into a “tutorial-posting” object<\/i><\/a> perhaps, is two data members, of relevance, that are URLs, that being …<\/p>\n

      \n
    1. the URL to the WordPress blog posting tutorial … and …<\/li>\n
    2. the URL to “the cut to the chase” intention of the WordPress blog posting tutorial<\/li>\n<\/ol>\n

      … and what we’re proposing today, is that a lot of users can easily forgo the “blurb” and “cut to the chase”, perhaps going back to the blurb for a further read should they want to delve further after a “cut to the chase” session.<\/p>\n

      We wanted a way to present this idea on our RJM Programming landing page<\/a>. There must be a way to add another HTML select<\/a> “dropdown” element to facilitate this? Well, yes, that could be done, but we thought it would be better to dedicate another RJM Programming Landing Page “clone” webpage that has a “cut to the chase” HTML select “dropdown” element substituted for its “listed and clickable” existing HTML select “dropdown” element, and then set it up that either web page can get you to the other “clone” web page, and to the user all they “feel” is the toggling of the “dropdown” data content.<\/p>\n

      So we just used the term “data content”, and that means you need to delve into where the “data” is from. With a WordPress blog, the “data” is from a MySql database, and to do anything about any changes here will revolve around involving a server side language like PHP … no way around that. So what we do is …<\/p>\n