More actions
John Hache (talk | contribs) m Added comments on training, software |
Ttenbergen (talk | contribs) No edit summary |
||
Line 8: | Line 8: | ||
We initially discussed structured data at https://docs.google.com/drawings/d/16E_dQl49fSxUUn56r9HlNHrkBPIoHwUPkqT33hlPAwM/edit, this is not fully what has been implemented. | We initially discussed structured data at https://docs.google.com/drawings/d/16E_dQl49fSxUUn56r9HlNHrkBPIoHwUPkqT33hlPAwM/edit, this is not fully what has been implemented. | ||
Do we want to include software, which machines it's available on, VPS access? I think those might be special cases of tools...This could potentially be useful for members to add their own tips and tricks. At bare minimum, we should have a page for CorelDraw as new members will likely want to use it for the lasers and Roland printer. Fusion360 would also be a nice page to have. Beyond that, they could probably be added onto the tool pages (like the slicer software instructions being added to 3D printers) | {{Discuss | | ||
* Do we want to include software, which machines it's available on, VPS access? I think those might be special cases of tools... | |||
** This could potentially be useful for members to add their own tips and tricks. At bare minimum, we should have a page for CorelDraw as new members will likely want to use it for the lasers and Roland printer. Fusion360 would also be a nice page to have. Beyond that, they could probably be added onto the tool pages (like the slicer software instructions being added to 3D printers) | |||
}} | |||
== some stuff I started experimenting with == | == some stuff I started experimenting with == |
Revision as of 11:02, 2024 July 23
You have to have an account to edit this wiki. To get an account, contact anyone with admin rights to set one up. Adding users to the admin group should be approved by member council.
If you have ideas on how to improve the wiki, for the most part just do it. Edits that break functionality may be reverted or fixed; editors should communicate when that is necessary.
Structure
For now the wiki is a list of Tools and their Maintenance and Broken data. If you think other things should be added, add them.
We initially discussed structured data at https://docs.google.com/drawings/d/16E_dQl49fSxUUn56r9HlNHrkBPIoHwUPkqT33hlPAwM/edit, this is not fully what has been implemented.
some stuff I started experimenting with
- Template:Hazard / Breathing hazard / Template:Hazard type
- Broken / Template:Broken / Broken:0845025035 A different namespace that can be edited without login; template only stores the broken info and it would be shown on the tool via query. I shelved this when I realized we needed to think further through how we would possibly transition to this, and that this might be better as a second or later step.
- Maintenance / Template:Maintenance log - I am not sure Jeff would be up for this. I would have to come up with a very-low-overhead solution. And we would still need to understand how it would be used and how it would work. The idea was to track both needed and performed maintenance in this, for both ad-hoc/break and regular maintenance. What tools take up a lot of our time?
- Training
- How much of that do we want on here? Do we want the trainers? Do we want to use this as a trainee record? What would our privacy thoughts be on that part? At least a training outline would be good, that way future trainers will know what is covered during the course and trainers/trainees can make sure the trainer has covered everything.
- Added current Training Sessions and Trainers
- Mediawiki extension Lockdown - This can be used to make parts of the wiki not overtly public, but think of it more like someone would have to stand on their toes to peek in than true privacy, wikis are not meant for that.
- Test tool has some other things, such as Instructions:Test tool linked in, and a sub page Test tool/SWP.
Extensions etc
This wiki uses Mediawiki extension Cargo to encode structured data so it can be updated automatically on lists via queries. Feel free to add additional structured data. Chat with Tina if you would like to learn more.
It also uses Mediawiki extension PageForms to make the "edit with form" happen.
It also uses the Citizen skin. For now anyway, it has some bugs I don't like. I have also worked with the Chameleon skin, or we could revert to the mediawiki standard vector skin, or any other skin we want to try.