{"id":17861,"date":"2022-07-19T01:13:25","date_gmt":"2022-07-19T05:13:25","guid":{"rendered":"https:\/\/pacificopencourses.col.org\/edt4ol\/?page_id=17861"},"modified":"2022-07-19T01:13:25","modified_gmt":"2022-07-19T05:13:25","slug":"tips-for-authoring-sub-pages","status":"publish","type":"page","link":"https:\/\/pacificopencourses.col.org\/edt4ol\/learning-challenges\/authoring-a-learning-sequence\/tips-for-authoring-sub-pages\/","title":{"rendered":"Tips for authoring sub-pages"},"content":{"rendered":"
\n
\n
\n
\n
\n
\n
\n
\"HTML-screenshotA.jpg\"<\/a><\/div>\n


<\/p>\n

On this course, you are not required to learn HTML markup. However there are a couple of handy wiki markup tips you can use to improve page layout. In this section, we also provide tips for improving layout of pages for mobile responsive design.\n<\/p>\n

Useful wiki markup code<\/span><\/h2>\n\n\n\n\n\n\n
Markup\n<\/th>\nPurpose\n<\/th>\n<\/tr>\n
<br>\n<\/td>\nSingle forced line break<\/i><\/p>\n

Sometimes the author must manually insert a line break to force the text which follows to start on a new line.\n<\/p>\n<\/td>\n<\/tr>\n

<nowiki> … <\/nowiki>\n<\/td>\nTo force the wiki to ignore (or ‘escape’) the effect of wiki markup contained between the opening and closing <nowiki> tags<\/i><\/p>\n

For example, when an author wants to show the raw wiki markup, instead of the wiki applying the relevant formatting in the published view.\n<\/p>\n

Note that the <\/nowiki> tags must be applied on every line where it is needed.\n<\/p>\n<\/td>\n<\/tr>\n

{{Clear}}\n<\/td>\nTo stop text that appears immediately after the insertion of this template from wrapping around a floating element like an image.<\/i><\/p>\n

For example, this is used with images to force text to appear below the image on a new line without text wrapping[1]<\/a><\/sup>.\n<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Images and mobile devices<\/span><\/h2>\n

When authoring online materials it’s important to remember that the user may be viewing the content using a different screen size to the one you are using for developing the materials. Bear in mind that the layout displayed on the user’s screen will vary depending on the screen size of the display device and as a developer it is hard to predict what screen the student will be using.\n<\/p>\n

Note that images that use the ‘Frame’ or ‘Thumb’ attribute in the wiki markup do not<\/b> automatically resize for different display widths on the WordPress site. Consequently we recommend that you avoid using framed or thumbnail images, where possible, to circumvent this challenge.\n<\/p>\n

Remember that the view port size of mobile phones in portrait view vary. The display width of the average mobile phone in portrait view ranges between 320 pixels and 414 pixels. So to avoid awkward wrapping of text around images on a mobile phone in portrait view, we recommend using an image markup that supports automatic resizing of the image to fit the display port if the image width is wider than the phone display.\n<\/p>\n

As a rule of thumb, we recommend that you use the following markup for the majority of images:\n<\/p>\n

[[image:name_of_file.png|414px|right]]<\/code>\n<\/pre>\n
Footnotes<\/span><\/h2>\n
    \n
  1. \u2191<\/a><\/span> This is the equivalent of the HTML tag: <br style=”clear:both;” \/><\/span>\n<\/li>\n<\/ol>\n
    <\/p>\n
    \n<\/div>\n
    <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/div>\n<\/div>\n<\/div>\n
    \n
    \n