Wiki 101: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
mNo edit summary
No edit summary
Line 1: Line 1:
{{Hint|See [[Wiki Cheatsheet]] for wiki editing cheatsheet.}}
{{Hint|This page under heavy edit. See [[Wiki Cheatsheet]] for wiki editing cheatsheet.}}


This Wiki 101 page will be one of the steps on the [[New_Developer_Orientation]] checklist. Working document for the script is @ https://docs.google.com/document/d/1FDUb25_uALUT9bFyAeFP_thSIn_k_VbcAfpaNf5tBBA/edit# and will generally follow the same outline as this page.
=General Introduction=
Our [[101 101's|101Pages]] are growing repositories of how-to's and modules based on our developing usage of these tools. In the future they may evolve into full courses with associated badges. Note for editors: at first, we might use this as a repository of links, but the goal is to increase usability by consolidating and assimilating help resources into a single page (so that a user does not need to open 1/2 dozen links to find a solution).  


The self verifying test for Wiki 101 will be the creation, formatting, and population of the Developer's log (the general steps in section 3 @ [[New_Developer_Orientation]]) as well as adding their information to [[OSE_Developers]].  By following the steps in this 101, you will have created your log and completed the test.
For now this 101 covers how-to's for creating a basic log for the [[Developer Test]], setting up your log during the [[New Developer Orientation]], and other tasks, and lastly, helpful links.


=Wiki 101 Class and Self Verifying Test=
=How to Make a Basic Log for the Developer Test =
Terminal Learning Objective: Understand the basics of MediaWik
For the [[Developer Test]] the applicant learns the basics of MediaWiki to create and name a basic log, add one entry, and upload a file. The following guide and upcoming video will walk you through these steps. 
(Insert <2 min Video)


Enabling Learning Objective: Pass the self verifying test by creating your log page and populating it with links and media.
#Get an account by requesting Access
#Create a wiki page (Protocol: First name + Log)
#Toggle view and edit modes
#Add a heading (Protocol on date format)
#Upload your cube file
#Embed the file in the log  


==Creating a Wiki Account==
=How to Complete Onboarding: Format Log and Add Bio=
To edit the wiki you will need to create an account. To do this
#Post your badge  
#Add Links


==Creating a Wiki Page (“Log_Example”)==
First, we will create your Log page.  I am going to be creating “Example Log” for you, but you will navigate to the as yet uncreated page for your own log, with the format ‘Yourname Log’ in the same place as my name in the navigation bar. You may also navigate to a red link, which indicates the link leads to a page that does not yet exist.
(altered from https://en.wikipedia.org/wiki/Wikipedia:How_to_create_a_page will shorten all the relevant methods or use the wiki instructions on our own wiki instructions page)
==Basic format==
Now that your log page is created, you will need to know how OSE work logs are structured.


To aid in learning to format your log and other Wiki pages, please review the following Wiki reference material.  We will also be posting links to these in the header of your work log
=Help Links=
Please review the following Wiki reference material.   
[[Wiki_instructions#Style_Guidelines]]
[[Wiki_instructions#Style_Guidelines]]
[[Wiki Cheatsheet]]
[[Wiki Cheatsheet]]
Line 27: Line 29:
[https://www.mediawiki.org/wiki/Help:Formatting Wiki Formatting Help]
[https://www.mediawiki.org/wiki/Help:Formatting Wiki Formatting Help]
[https://www.mediawiki.org/wiki/Help:Images Picture Editing Help]
[https://www.mediawiki.org/wiki/Help:Images Picture Editing Help]
[https://en.wikipedia.org/wiki/Wikipedia:How_to_create_a_page]


[[Example Log]] is the log created in the tutorial videos, and to help keep logs consistent and easy to navigate, this is the format you should use.  Notice that after the header, the latest is on top so that someone looking at your page can see your most recent work immediately.  Note also that the date format for each entry uses the three letter weekday, three letter month, day, and four digit year, and any times use 24 hour time and note your timezone.   
[[Example Log]] is the log created in the tutorial videos, and to help keep logs consistent and easy to navigate, this is the format you should use.  Notice that after the header, the latest is on top so that someone looking at your page can see your most recent work immediately.  Note also that the date format for each entry uses the three letter weekday, three letter month, day, and four digit year, and any times use 24 hour time and note your timezone.   
Line 45: Line 48:


Post a public email address for yourself
Post a public email address for yourself


==Insert a picture==
==Insert a picture==

Revision as of 02:26, 17 July 2017


HintLightbulb.png Hint: This page under heavy edit. See Wiki Cheatsheet for wiki editing cheatsheet.

General Introduction

Our 101Pages are growing repositories of how-to's and modules based on our developing usage of these tools. In the future they may evolve into full courses with associated badges. Note for editors: at first, we might use this as a repository of links, but the goal is to increase usability by consolidating and assimilating help resources into a single page (so that a user does not need to open 1/2 dozen links to find a solution).

For now this 101 covers how-to's for creating a basic log for the Developer Test, setting up your log during the New Developer Orientation, and other tasks, and lastly, helpful links.

How to Make a Basic Log for the Developer Test

For the Developer Test the applicant learns the basics of MediaWiki to create and name a basic log, add one entry, and upload a file. The following guide and upcoming video will walk you through these steps. (Insert <2 min Video)

  1. Get an account by requesting Access
  2. Create a wiki page (Protocol: First name + Log)
  3. Toggle view and edit modes
  4. Add a heading (Protocol on date format)
  5. Upload your cube file
  6. Embed the file in the log

How to Complete Onboarding: Format Log and Add Bio

  1. Post your badge
  2. Add Links


Help Links

Please review the following Wiki reference material. Wiki_instructions#Style_Guidelines Wiki Cheatsheet Daily_Log_of_Tasks Wiki Formatting Help Picture Editing Help [1]

Example Log is the log created in the tutorial videos, and to help keep logs consistent and easy to navigate, this is the format you should use. Notice that after the header, the latest is on top so that someone looking at your page can see your most recent work immediately. Note also that the date format for each entry uses the three letter weekday, three letter month, day, and four digit year, and any times use 24 hour time and note your timezone. Create a headline for the date like I am doing now by either bracketing your date in double equals signs or click this uppercase 'A' icon above the text entry box, which will create a level 2 headline.

(Publish early & often. Always link / embed files, even if you're not done. Put your newest work on top. Style-wise, keep it short and sweet like post-it notes on progress.) Review Best Practices for Logs.

Add links

Link to the following top of your log (for quick reference): Wiki Formatting Help if you might need it. Add the Timesheet link. This is how we submit time sheets every Monday. Add the Google Hangouts link. This is where we meet. Add the D3D for the general 3D printer project overview. Add the Development Team Log. This is where we keep all our working files and link our captured meeting videos (if you happen to miss one). Add your teammates' logs. At the first meeting you will be assigned to a team. Once you find out, refer to the Developer’s Page to find the links to their logs, and link to them on top of your page. Add the OSE Network. This is our official discussion thread.

Post a public email address for yourself

Insert a picture

Post your badge at the top of your log.

Uploading files (upload a picture of yourself?)

Version History understanding- uploading files over an existing files, be bold in changing things we can always revert