If your company primarily stores content in Google Drive, it can be helpful to create a guide that clearly defines what should be kept in its original Google Drive form and what should be made into Cards.
Check out this Best Practices article with helpful examples about the type of content to create directly in Guru vs. attach from another source.
Reasons to replace a Google Drive asset with a Guru Card:
Keep knowledge up to date via Guru's verification process.
Maintain organization and reduce the amount of lost information.
Drive better adoption rates, having information found in the first place people search re-affirms Guru's value for your team.
Searchability: bite-size knowledge in Guru Cards is easier to quickly search for than long-standing docs across file folders.
We recommend embedding (or linking to) a Google Drive asset:
If it is written in long-form content (think, a research document)
If it is a particular-use program that has specific editing capabilities for that asset (think, a Google Sheet)
Best practices for structuring Cards with embedded or linked Google Drive assets:
Make it searchable. Give the card a title and tag(s) that reflect the Google Drive asset that’s inside.
Provide context on what the asset is about, what it should be used for, and what audience it is targeting.
You can also embed iFrames or link out to the doc/spreadsheet/slides so that your team can scroll through the asset without leaving the Guru Card.
Google Drive files that are embedded in Guru will not appear in Guru search results. File attachments will appear in search, however, so if you attach the file in addition to embedding it, those results will show in search results.
If you want the Google Drive links to be public (to share with an external source for example) make the file public to the web OR visible to anyone with the link. Learn more about Google link sharing.
📑 Related articles