If a web-based application or command line options are not a fit for your workflow, desktop clients are another option to transfer data. While these options are not ARCC provided tools, we have tested many of them and can provide some support for users of them. Clients that ARCC have tested are MobaXTerm, Cyberduck, and Cloudberry (MSP 360 explorer), but for this module, we will only use Cyberduck in our examples due to it being available for Windows and Mac operating systems.
Headers and Sections
Each sections should start with a header of ‘Heading 1’. This helps to make sure that the Table of Contents operates like an agenda. Also it helps when we “advance a slide” it jumps to the top of the section. Each section should be limited in length to no more than 14 lines of straight text to ensure that when presenting it can be viewed as a “Slide”.
This is 14 lines A.K.A the End.
Code Examples
Two Column Tables are nice ways to separate content/ Background info along with a code example on the same “Slide”. Please notice the table width. This should stop scroll bars from appearing
| Please use the "code snippet" in the + button when creating code examples. Also please do not go past the width of the table. This is to prevent scroll bars appearing This is the Max number of code lines to show on an example |
Straight Code - No context
Limit to 16 lines in the example. This is the end
Same Thing With Images
Two Column Tables are nice ways to separate content/ Background info along with an image example on the same “Slide”. Please notice the table width. This should stop scroll bars from appearing
|
Alternatively No Table
Finally The End
Link to Previous sub-module or Home Module | Align left link to next sub-module or home |