Purpose of Portland NETwiki: Difference between revisions
From Portland NET Wiki
mNo edit summary |
mNo edit summary |
||
| Line 9: | Line 9: | ||
* '''Preservation and accessibility of institutional knowledge:''' Portland NET is the outcome of over 30 years of volunteer and PBEM staff expertise. Prior to NETwiki, much of this institutional knowledge was locked up in the heads of volunteers or under layers of nearly forgotten electronic files stored on PBEM drives and inaccessible to the wider NET community. Today, PBEM and NET can use NETwiki as a platform to establish, expand, and refine expertise and knowledge. | * '''Preservation and accessibility of institutional knowledge:''' Portland NET is the outcome of over 30 years of volunteer and PBEM staff expertise. Prior to NETwiki, much of this institutional knowledge was locked up in the heads of volunteers or under layers of nearly forgotten electronic files stored on PBEM drives and inaccessible to the wider NET community. Today, PBEM and NET can use NETwiki as a platform to establish, expand, and refine expertise and knowledge. | ||
* '''Saved PBEM staff time:''' An inordinate amount of PBEM staff time was spent writing emails to volunteers answering narrow questions about program protocols or best practices for response. Today, PBEM staff can publish much of that information to NETwiki and send volunteers links to comprehensive articles instead of calling up all the information or research needed in order to complete a reply. With that time saved, PBEM staff has increased capacity to respond to other volunteer requests and program needs. | * '''Saved PBEM staff time:''' An inordinate amount of PBEM staff time was spent writing emails to volunteers answering narrow questions about program protocols or best practices for response. Today, PBEM staff can publish much of that information to NETwiki and send volunteers links to comprehensive articles instead of calling up all the information or research needed in order to complete a reply. With that time saved, PBEM staff has increased capacity to respond to other volunteer requests and program needs. | ||
* | * '''Quick and easy edits:''' A Wiki allows team members to update or correct content on the fly, ensuring that information stays current without requiring specialized technical skills (as was needed for the NET Guidelines, which was published through Adobe InDesign). | ||
* - | * '''User-friendly interface:''' The familiar, web-based format is easy to navigate for volunteers and staff alike, offering a more approachable alternative to complex platforms like WebEOC. | ||
* '''Offline capability:''' Wiki content can be exported or mirrored for offline use, supporting continuity of operations in disconnected environments, such as over the AREDN mesh network. | |||
* '''Supports rich content:''' Wikis can host a wide range of media—text, images, videos, documents, and hyperlinks—making it easier to share training materials, guides, and operational protocols in one place. | |||
