Forum Discussion
Tormod Solem Slupphaug
Jun 15, 2021Iron Contributor
Company procedures and policies: documents vs pages?
Hi. I'm about to move all our company's procedures and policies over to SharePoint, but I'm wondering if I should use a Document Library or Pages. All procedures / policies mostly follow the same...
- Mar 12, 2024When we're looking at moving our company's procedures and policies over to SharePoint, we're essentially faced with two paths: Document Libraries or Pages. It's not just a choice between two features; it's about picking the tool that matches how we work and what we need from our documents. So, Document Libraries, that's the traditional route. It's what most people are already used to. You get the benefit of offline access, which is great for anyone who needs to take these documents on the go or share them outside our SharePoint environment. Plus, SharePoint's got this solid setup for tracking changes to documents, which can be a lifesaver. The downside? Well, it's not the easiest to sift through on mobile, and updating documents involves a few extra steps.
Then, there's Pages. This is the modern approach. It's built with today's web and mobile use in mind, making information more accessible and engaging. You can easily add videos, links, or images, which could make our policies more interesting to read. Also, finding stuff is generally easier with Pages. The trade-offs? It might take a bit for everyone to get used to this new way of looking at our policies. And if you need to access these offline, it's not as straightforward. So, what's the best path? It really depends on what's more important for us. Do we need that traditional, familiar format that's easy to take offline and share? Or, are we leaning towards something more modern and accessible, even if it means a bit of a learning curve and figuring out a workaround for offline access?
There's no one-size-fits-all answer here. It's about finding the right fit for our team's needs and how we like to work with our content.
BarryGoblon
Mar 12, 2024Iron Contributor
When we're looking at moving our company's procedures and policies over to SharePoint, we're essentially faced with two paths: Document Libraries or Pages. It's not just a choice between two features; it's about picking the tool that matches how we work and what we need from our documents. So, Document Libraries, that's the traditional route. It's what most people are already used to. You get the benefit of offline access, which is great for anyone who needs to take these documents on the go or share them outside our SharePoint environment. Plus, SharePoint's got this solid setup for tracking changes to documents, which can be a lifesaver. The downside? Well, it's not the easiest to sift through on mobile, and updating documents involves a few extra steps.
Then, there's Pages. This is the modern approach. It's built with today's web and mobile use in mind, making information more accessible and engaging. You can easily add videos, links, or images, which could make our policies more interesting to read. Also, finding stuff is generally easier with Pages. The trade-offs? It might take a bit for everyone to get used to this new way of looking at our policies. And if you need to access these offline, it's not as straightforward. So, what's the best path? It really depends on what's more important for us. Do we need that traditional, familiar format that's easy to take offline and share? Or, are we leaning towards something more modern and accessible, even if it means a bit of a learning curve and figuring out a workaround for offline access?
There's no one-size-fits-all answer here. It's about finding the right fit for our team's needs and how we like to work with our content.
Then, there's Pages. This is the modern approach. It's built with today's web and mobile use in mind, making information more accessible and engaging. You can easily add videos, links, or images, which could make our policies more interesting to read. Also, finding stuff is generally easier with Pages. The trade-offs? It might take a bit for everyone to get used to this new way of looking at our policies. And if you need to access these offline, it's not as straightforward. So, what's the best path? It really depends on what's more important for us. Do we need that traditional, familiar format that's easy to take offline and share? Or, are we leaning towards something more modern and accessible, even if it means a bit of a learning curve and figuring out a workaround for offline access?
There's no one-size-fits-all answer here. It's about finding the right fit for our team's needs and how we like to work with our content.