You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 5, 2021. It is now read-only.
At the moment, Driveshaft lets you specify a Google Spreadsheet that lists other Drive files to use as an index page, which can work for an organization that keeps a shared collection of files. But because it's asynchronous (it needs to be published to S3), and has to be manually entered, it's less useful for individuals.
An alternative might be to render a user's available drive files on the index page? Rendering the contents of a shared folder might also be useful, and might even be more relevant for an organization than the current setup.
The text was updated successfully, but these errors were encountered:
Would it be a solution to just add a row to the index sheet using the Drive API every time a new spreadsheet is published? That way editors could get an overview in the Google doc or in the index page. And deleting old/static documents from the Google doc would remove them from the index page. Maybe..
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment, Driveshaft lets you specify a Google Spreadsheet that lists other Drive files to use as an index page, which can work for an organization that keeps a shared collection of files. But because it's asynchronous (it needs to be published to S3), and has to be manually entered, it's less useful for individuals.
An alternative might be to render a user's available drive files on the index page? Rendering the contents of a shared folder might also be useful, and might even be more relevant for an organization than the current setup.
The text was updated successfully, but these errors were encountered: