{"id":620,"date":"2013-05-09T11:20:38","date_gmt":"2013-05-09T11:20:38","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/?page_id=620"},"modified":"2018-11-19T12:28:14","modified_gmt":"2018-11-19T12:28:14","slug":"authorhelp","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/software\/authorhelp\/","title":{"rendered":"Help for Authors"},"content":{"rendered":"<h2>Editing a new Application Page<\/h2>\n<p>New application pages will be initially created by the RI team. This will include common section headings. <\/p>\n<h3>Logging in to WordPress<\/h3>\n<p>The <em>csf-apps<\/em> WordPress site is a standalone WP site (even though it looks like part of the entire CSF documentation site). We can give you <em>Author<\/em> rights to this site enabling you to edit WordPress <em>pages<\/em>.<\/p>\n<ol>\n<li>Log in to this site by following the <em>log in<\/em> link in the bottom right corner of any page. You will be presented the same page but this time with the editing menus along the top in a dark grey bar.<\/li>\n<\/ol>\n<h3>Finding and Editing an Application&#8217;s Page<\/h3>\n<ol>\n<li>If you are currently on the page you wish to edit, simply click on <em>Edit Page<\/em> in the grey bar at the top.\n<li>Otherwise, navigate to the required apps page using the site&#8217;s menus<\/li>\n<li>In the grey WordPress bar click on &#8220;Edit Page&#8221;.<\/li>\n<li>You will now be in the WordPress editor<\/li>\n<\/ol>\n<h3>Writing HTML<\/h3>\n<p>WordPress does not use wiki-style markup. Instead you can use the &#8220;Visual&#8221; Editor for wysiwyg-style editing or use the &#8220;Text&#8221; Editor to write the usual HTML tags (look at the top-right of the edit box &#8211; there are two little tabs to switch between the different styles of editor). I prefer the &#8220;Text&#8221; editor so I can see exactly which tags are being used and where. <\/p>\n<h4>New Application Template Text<\/h4>\n<p>Paste the following in to the editor<\/p>\n<pre>\r\n&lt;h2&gt;Overview&lt;\/h2&gt;\r\n\r\n&lt;a href=\"\"&gt;APP&lt;\/a&gt; is a program to\r\n\r\nVersion N.M is installed on the CSF.\r\n\r\n&lt;h2&gt;Restrictions on use&lt;\/h2&gt;\r\n\r\nDetails of the licence, restrictions, links to licence docs etc\r\n\r\n&lt;h2&gt;Set up procedure&lt;\/h2&gt;\r\n\r\nTo access the software you must first load the modulefile:\r\n\r\n&lt;pre&gt;\r\nmodule load apps\/path\/to\/module\/n.m\r\n&lt;\/pre&gt;\r\n\r\n&lt;h2&gt;Running the application&lt;\/h2&gt;\r\n\r\nPlease do not run XXX on the login node. Jobs should be submitted to the compute nodes via batch.\r\n\r\n&lt;h3&gt;Serial batch job submission&lt;\/h3&gt;\r\n\r\nMake sure you have the modulefile loaded then create a batch submission script, for example:\r\n\r\n&lt;pre&gt;\r\n#!\/bin\/bash\r\n#$ -S \/bin\/bash\r\n#$ -cwd             # Job will run from the current directory\r\n#$ -V               # Job will inherit current environment settings\r\n\r\nAPP arg1 arg2 &gt; out.log\r\n&lt;\/pre&gt;\r\n\r\nSubmit the jobscript using: \r\n\r\n&lt;pre&gt;qsub &lt;em&gt;scriptname&lt;\/em&gt;&lt;\/pre&gt;\r\n\r\nwhere &lt;em&gt;scriptname&lt;\/em&gt; is the name of your jobscript.\r\n\r\n&lt;h3&gt;Parallel batch job submission&lt;\/h3&gt;\r\n\r\nGiven an example parallel jobscript, including suitable PE\r\n\r\n&lt;h2&gt;Further info&lt;\/h2&gt;\r\n\r\n&lt;ul&gt;\r\n  &lt;li&gt;&lt;a href=\"\"&gt;APP website&lt;\/a&gt;&lt;\/li&gt;\r\n&lt;\/ul&gt;\r\n\r\n&lt;h2&gt;Updates&lt;\/h2&gt;\r\n\r\nNone.\r\n\r\n<\/pre>\n<h4>HTML hints<\/h4>\n<p>However, there are some rules to simplify things:<\/p>\n<p>Links &#8211; we automatically add an icon to external links. There are two styles:<\/p>\n<ol class=\"gaplist\">\n<li>Icons on external links\n<ul>\n<li>An external \/ off-site link such as <a href=\"http:\/\/www.intel.com\">Intel website<\/a>. Ensure you use the <code>http:\/\/<\/code> protocol in the link tag &#8211; for example\n<pre>&lt;a href=\"http:\/\/www.intel.com\"&gt;Intel website&lt;\/a&gt;<\/pre>\n<\/li>\n<li>A link to another RI website such as <a href=\"http:\/\/ri.itservices.manchester.ac.uk\/redqueen\">Redqueen docs<\/a>. Ensure you use <code>&lt;a href=\"http:\/\/ri.itservices.manchester.ac.uk\"&gt;<\/code> at the start of the link tag &#8211; for example\n<pre>&lt;a href=\"http:\/\/ri.itservices.manchester.ac.uk\/redqueen\"&gt;Redqueen docs&lt;\/a&gt;<\/pre>\n<\/li>\n<li>A link within this site (no icon applied) such as <a href=\"\/csf-apps\/software\/modules\">Modulefile help<\/a>. Do not use <code>http:\/\/ri.itservices.manchester.ac.uk<\/code> in the link tag. Instead use something like\n<pre>&lt;a href=\"\/csf-apps\/software\/modules\"&gt;Modulefile help&lt;\/a&gt;<\/pre>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Paragraph tags<\/strong>: <strong>Do not<\/strong> use paragraph tags &lt;p&gt;&#8230;&lt;\/p&gt; even if writing raw HTML in the &#8220;Text&#8221; editor. WordPress will put them in automatically. You can simply type paragraphs of text (with blank lines above and below) in the both the &#8220;Visual&#8221; editor and &#8220;Text&#8221; editor.<\/li>\n<li><strong>H1 tags<\/strong>: <strong>Do not<\/strong> use a <em>heading 1<\/em> &lt;h1&gt;&#8230;&lt;\/h1&gt; title. WordPress will add this automatically.<\/li>\n<ul>\n<li>The H1 title is initially set to be the same as the title entered in to the box near the very top of the page (just below the large &#8220;Edit Page&#8221; header). You <strong>can<\/strong> edit this to change the H1 title of the page.<\/li>\n<\/ul>\n<li><strong>Do not<\/strong> edit the &#8220;Permalink&#8221; setting (above the main page editor).<\/li>\n<li><strong>Do not<\/strong> change the &#8220;Parent&#8221; setting in the &#8220;Page Attributes&#8221; panel (right hand side). This should always be set to &#8220;Applications&#8221;. We arrange the grouping \/ categorisation of applications elsewhere in WordPress (in the Menu editor). Changing the &#8220;Parent&#8221; will modify the page&#8217;s URL (which we will have set up for you).<\/li>\n<li><strong>Code\/commands<\/strong>: To enter a section of user commands in fixed-width font style use a &lt;pre&gt; tag. It will be automatically indented so <strong>do not<\/strong> put spaces in front of each command, especially if giving an example of a jobscript as this introduce errors if the user copies and pastes your code in to their own file.<\/li>\n<li><strong>Code\/commands in lists<\/strong>: Using a &lt;pre&gt; tag inside a list works corretly. I generally put the &lt;pre&gt; &#8230; &lt;\/pre&gt; <strong>inside<\/strong> the &lt;li&gt; &#8230; &lt;\/li&gt; tags, as follows: following:\n<pre>\r\n&lt;ul&gt;\r\n  &lt;li&gt;Here are some commands:\r\n&lt;pre&gt;\r\n.\/myprog   # no spaces at start of this line\r\n.\/date     # nor this one\r\n&lt;\/pre&gt;&lt;\/li&gt;\r\n  &lt;li&gt;More list items...&lt;\/li&gt;\r\n&lt;\/ul&gt;\r\n<\/pre>\n<\/li>\n<li><strong>Lists<\/strong>: If doing a list with long list items (like this one!) you can add spacing between each list item by using <code>&lt;ol class=\"gaplist\"&gt;<\/code> or <code>&lt;ul class=\"gaplist\"&gt;<\/code>.<\/li>\n<li><strong>Comments<\/strong>: <strong>Do not<\/strong> use HTML comment tags &lt;&#8211; &#8230; &#8211;&gt; as this breaks WordPress page rendering in most cases. To hide entire lines (possibly more than one) use <code>&lt;div class=\"comment\"&gt; ... &lt;\/div&gt;<\/code>. You can also use this class in a &lt;span&gt; tag to comment out words <em>within<\/em> a single line.<\/li>\n<\/ol>\n<h3>Saving your Edits<\/h3>\n<p>Press &#8220;Update&#8221; on the right-hand-side. You will still be in the editor after WordPress has saved your work but there should be a message at the top of the screen indicating the page was saved.<\/p>\n<p>To view the page select &#8220;View Page&#8221; in the black bar at the top of the screen.<\/p>\n<p>To preview the page before saving select &#8220;Preview Changes&#8221; on the right-hand-side. This usually opens a new window in which to show the preview. Don&#8217;t forget to save your changes back in the original window.<\/p>\n<p>more to come&#8230;.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Editing a new Application Page New application pages will be initially created by the RI team. This will include common section headings. Logging in to WordPress The csf-apps WordPress site is a standalone WP site (even though it looks like part of the entire CSF documentation site). We can give you Author rights to this site enabling you to edit WordPress pages. Log in to this site by following the log in link in the.. <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/software\/authorhelp\/\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":8,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"members.php","meta":{"footnotes":""},"class_list":["post-620","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/pages\/620","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/comments?post=620"}],"version-history":[{"count":20,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/pages\/620\/revisions"}],"predecessor-version":[{"id":3058,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/pages\/620\/revisions\/3058"}],"up":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/pages\/8"}],"wp:attachment":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf-apps\/wp-json\/wp\/v2\/media?parent=620"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}