Difference between revisions of "Editing the Wiki"
Poofjunior (talk | contribs) |
Poofjunior (talk | contribs) |
||
Line 43: | Line 43: | ||
====PDFs hosted on Github==== | ====PDFs hosted on Github==== | ||
− | Links to PDFs hosted on Github will redirect to a github rendering of the PDF as a PNG image on Github's website. | + | Links to PDFs hosted on Github will redirect to a github rendering of the PDF as a PNG image on Github's website like [https://github.com/machineagency/jubilee/blob/master/frame/assembly_instructions/toolchanger_mechanism/toolchanger_lock_assembly_instructions.pdf this]. Ideally, it would be nice to click on a PDF link that redirects us to a print-ready page that just shows the PDF like [https://docs.google.com/viewer?url=github.com/machineagency/jubilee/raw/master/frame/assembly_instructions/toolchanger_mechanism/toolchanger_lock_assembly_instructions.pdf this]. We can create this effect by modifying the Github link to get Google's PDF doc viewer to render it cleanly in a format that can be readily printed. To do this, prefix the github URL with the following: |
https://docs.google.com/viewer?url= | https://docs.google.com/viewer?url= | ||
− | Then, in the url, change '''blob''' to '''raw'''. When the page is saved, the result should be a link that, when clicked presents a preview of the PDF as if it were ready to be printed. | + | Then, in the github url, change '''blob''' to '''raw'''. When the page is saved, the result should be a link that, when clicked presents a preview of the PDF as if it were ready to be printed. |
Revision as of 12:28, 3 July 2020
All are welcome to edit the wiki, but do read these guidelines first, or your changes may be reverted!
Wiki Goals
The primary goal of the wiki is the creation and sharing of knowledge related to working with Jubilee.
Syntax
The Jubilee Wiki uses the MediaWiki syntax, and a series of plugins or widgets to offer special conveniences like code boxes, etc.
Wiki Organization
In a MediaWiki, there's no strict page hierarchy. In other words, pages aren't organized into folders of folders. To loosely organize pages, we can create internal links on one page that will take you to another page. In this way, information is tightly connected, joined by links. Feel free to use internal links liberally.
Let's try to keep the wiki friendly to newcomers and frequent flyers. That is, keep frequently accessed information in the Sidebar. Make it easy to find. Examples include: Assembly instructions and Maintenance. Topics in the Sidebar should be broad (example: assembly instructions). They should be entry points for building Jubilee or understanding how Jubilee works. Topics deep in the page structure should be specific (i.e: tuning retraction settings on the Default Extruder).
Jubilee is aimed at a range of multitool applications. While Jubilee's most common use case is multi-material 3D printing, let's make sure that we preserve a page structure that provides equal entry points to other applications so they don't get buried.
Voice
Inclusivity
At all costs, avoid statements that are racist, sexist, homophobic, transphobic, culturally insensitive, or express hatred in any way.
Normative Statements
Avoid normative statements where possible. A normative statement is a statement that expresses a value judgement.
Example: You should ..
Example: garbage crimp connectors
Example: MIC6 Aluminum is better than 6061 aluminium
Instead, in the case where you, the author, feel this way, try to unpack why and lay out your reasoning. In the example above about MIC6 aluminum, what makes it better? What characteristics related to both the situation and the material make it a better choice?
Wiki Conventions
Project Versions
The wiki will always reference the most up-to-date version of the project. Information related to older versions should (1) either explicitly mention this up front or (2) create and older page and link to it from the current page.
Links and Uploads
Design Files
Design files are subject to change between versions. As such, do not upload design files directly to the wiki. Instead, link them to the file in the master branch of the project repository.
Exception: aesthetic-only or placeholder images that clearly point to the most up-to-date version are OK.
PDFs hosted on Github
Links to PDFs hosted on Github will redirect to a github rendering of the PDF as a PNG image on Github's website like this. Ideally, it would be nice to click on a PDF link that redirects us to a print-ready page that just shows the PDF like this. We can create this effect by modifying the Github link to get Google's PDF doc viewer to render it cleanly in a format that can be readily printed. To do this, prefix the github URL with the following:
https://docs.google.com/viewer?url=
Then, in the github url, change blob to raw. When the page is saved, the result should be a link that, when clicked presents a preview of the PDF as if it were ready to be printed.