Main Page: Difference between revisions
From WikiNET
mNo edit summary |
mNo edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 303: | Line 303: | ||
|- | |- | ||
|'''100.10.04''' | |'''100.10.04''' | ||
|[[Criminal Background]] | |[[Background Checks|Criminal Background Checks]] | ||
|- | |- | ||
|'''100.10.05''' | |'''100.10.05''' | ||
| Line 559: | Line 559: | ||
|style="padding-left: 1em;"|'''300.05.10.a''' | |style="padding-left: 1em;"|'''300.05.10.a''' | ||
|style="padding-left: 5em;"|[[Unmanned Aerial Vehicles (Drones)]] | |style="padding-left: 5em;"|[[Unmanned Aerial Vehicles (Drones)]] | ||
|- | |||
|style="padding-left: 1em;"|'''300.05.10.b''' | |||
|style="padding-left: 5em;"|[[Response to Persons with Disabilities]] | |||
|- | |- | ||
|'''300.05.11''' | |'''300.05.11''' | ||
| Line 1,234: | Line 1,237: | ||
The strength of Portland NET is its people: their knowledge and diversity of experience. By using a collaborative platform, a Wiki preserves institutional knowledge long after key PBEM staffers come and go. The Wiki does not supplement PBEM's community engagement; it is a '''''part of''''' PBEM's community engagement. It also saves staff and volunteer time by organizing collective knowledge into easy-to-find and send articles. | The strength of Portland NET is its people: their knowledge and diversity of experience. By using a collaborative platform, a Wiki preserves institutional knowledge long after key PBEM staffers come and go. The Wiki does not supplement PBEM's community engagement; it is a '''''part of''''' PBEM's community engagement. It also saves staff and volunteer time by organizing collective knowledge into easy-to-find and send articles. | ||
Add to that a Wiki's interlinking capabilities, ease of use and familiar formatting, capacity to present information that engages with multiple learning styles, and scalability, and it's easy to see why a Wiki would evolve into a critical part of the NET ecosystem. | Add to that a Wiki's interlinking capabilities, ease of use and familiar formatting, automated revision tracking, capacity to present information that engages with multiple learning styles, and scalability, and it's easy to see why a Wiki would evolve into a critical part of the NET ecosystem. | ||
