Set up Lullabot.com tugboat for final testing of ebook

[dsayswhat]

We'll need to lock a lullabot.com tugboat, and change its ebook content to point to the ebook site, and then have folks give it a look.

If it all looks good, we can dispose of the tugboat and make those content changes on lullabot.com, then we'll be live.

[jazzdrive3]

Has this been created anywhere? Looks like all of the issues have been resolved so far.

[dsayswhat]

It has not yet. If the ebook work is all up on github pages as of the most recent changes, then we probably just need to clone the base preview and lock it, so we can experiment with the content in Drupal and how it points to the ebook site.

[sirkitree]

ebooks.lullabot.com automatically deploys on commits to main so all is deployed already and you can test there. Pull requests will create tugboats. let me know if this needs to change, but I think it's probably sufficient for this small codebase

[dsayswhat]

As far as URLs go, do we link like this: https://ebooks.lullabot.com/ebooks/over-structured-content/chapters/chapter-1?

Or do we have some other URL that we should use when linking from Lullabot.com?

[sirkitree]

I think that landing on the cover of any book would probably be desired.

• https://ebooks.lullabot.com/ebooks/over-structured-content/cover
• https://ebooks.lullabot.com/ebooks/large-team-challenges/cover
• https://ebooks.lullabot.com/ebooks/rogue-university/cover

[dsayswhat]

OK. I have cloned the lullabot.com tugboat and locked it - our test instance is located at https://main-l7jp63yx57nh2hiz4xnejvtlihklgzow.tugboatqa.com.

A webform update is required to change the redirect to the new ebook.

Then visited the 'Overstructure your content' whitepaper node (our ebooks are whitepapers, for the uninitiated), and realized the necessary update update is on the webform side.

So, I visited the webform related to our whitepaper/ebook node, and found had to change the URL on the 'confirmation' settings page: https://main-l7jp63yx57nh2hiz4xnejvtlihklgzow.tugboatqa.com/admin/structure/webform/manage/how_to_avoid_over_structuring_yo/settings/confirmation

After save, I went back to the whitepaper node and submitted the form. It worked great, took me to the ebook as intended. Yay for us, and it looks great.

Other observations

I removed the removed the referenced pdf from the PDF Media field, no problem there.
However the download the PDF button still shows on the rendered whitepaper node. Looks like we'll need a theming adjustment to take out that link, or change the text to make it less PDF-centric.

Remaining action items:

• Update the other ebooks with their new URLs and test the forms.
• browse the ebooks, look for any other little issues and ticket them.
• decide with Ellie and Jared what to do with the 'Download the PDF' button on whitepaper/ebook nodes.

[sirkitree]

The messaging on https://github.com/Lullabot/lullabot.com-d8/blob/48c234191a1d43739d50137af0d67869c7ed401a/web/themes/custom/lullabot/components/01-atoms/forms/textfields/textfields.twig#L5 also states that we email the user with a link. I'm not sure how the email is sent, but we'll want to be sure to update that as well and test.

Looks like it might just be configuring the webform, but I'm not sure how we'll tell it which ebooks link to use: https://www.lullabot.com/admin/structure/webform/manage/gated_content/handlers

[jazzdrive3]

I'll take care of all the configuration changes on the Lullabot.com side of things. Those are easy updates in the webforms themselves and I'm familiar with it.

[sirkitree]

Anything left to do here?

[VeroTehanga]

@dsayswhat @jazzdrive3 Just to follow up on the comment above... any updates on this? cc. @sirkitree