Re: Public-facing documentation site?

[Margie Roswell]

Reposting my query for the third time:

• How can I make my library content accessible to the world (like https://nyt-library-demo.herokuapp.com/ ) 
• (Is there a way to remove 'edit' and other admin links just for non-logged-in people?)

Hoping someone has an answer (and can add it to the documentation)

Margie

--

http://HealthyCampaign.org

http://SugarWars.com

http://bit.ly/antiviral-nutrition

On Tue, Mar 24, 2020 at 6:34 PM Margie Roswell <mros...@gmail.com> wrote:

Reposting this question:

• How can I make my library content accessible to the world (like https://nyt-library-demo.herokuapp.com/ ) without giving the world my Google login credentials?
• Is there a way to o remove 'edit' and other admin links just for non-logged-in people?

Thanks,

Margie

--

http://CommitteeMaps.org

http://SugarWars.com

On Thu, Mar 12, 2020 at 12:50 PM Margie Roswell <mros...@gmail.com> wrote:

I have a post still held for moderation. Small update to that one:  I was eventually successful installing an instance of Library. 

I think I had to use: 

'gcloud datastore create-indexes ./index.yaml --project {{id}}'

even though create-indexes is listed in the documentation as deprecated. (Not actually sure if that's the piece that got me through, or if I had some other breakthrough and 'gcloud datastore indexes create ./index.yaml --project{{id}}' would've worked just as well.)

But now I've got one more question:

I'd like a public-facing documentation site, just like https://nyt-library-demo.herokuapp.com/ (Ideally with edit and other admin links removed unless we're logged in.)

How can I make my library content accessible to the world, without giving the world my email credentials?

Margie

--

http://CommitteeMaps.org

http://SugarWars.com

[Isaac White]

Hi Margie,

Sorry we missed your earlier messages. Library wasn't developed with a public use case in mind, so the features you describe aren't yet supported as simple configuration options. We're interested in adding that functionality in the future, but until then there are a few code customization pathways used by public Library sites which may do most of what you want.

You can override the default Library authentication behavior via the custom directory. In the case of nyt-library-demo.herokuapp.com, the authentication override skips any OAuth verification and stubs in demo...@example.com. This is what makes the demo site accessible to the world.

There's not a built in option to hide the Edit button, but some organizations have hidden it for all users via custom CSS. (Since the edit permissions for Library are managed from the Google Docs UI and not Library itself, hiding the button is mostly a cosmetic issue.) 

It might be possible to make the edit button display conditionally, but this gets harder because you'd need to write your own authentication middleware that only prompts login from a certain page/url, so that by default most visitors aren't forced to log in. 

Hope that's helpful.

Isaac

--
You received this message because you are subscribed to the Google Groups "NYT Library Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nyt-library-comm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nyt-library-community/CAPAc6WHZkABThxvUcuZWXodEpn7W%2BOHtt609%2Bix9cmNY5ryQXg%40mail.gmail.com.