Added LikeFeedbackBox back to ArticleReader. Changed prompt message.

[oskaitu]

Added the already existing LikeFeedbackBox back to ArticleReader. Proposed change to prompt message to user: "Would you like more articles like this?".

Tested by going into the route: "http://localhost:3000/render/read/article?id=22"

[netlify[bot]]

✅ Deploy Preview for voluble-nougat-015dd1 ready!

Name	Link
🔨 Latest commit	9e58db535b995fb13972fe5b8082140222f4d0e5
🔍 Latest deploy log	https://app.netlify.com/sites/voluble-nougat-015dd1/deploys/65f07bba9efa8b00089c8976
😎 Deploy Preview	https://deploy-preview-318--voluble-nougat-015dd1.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[oskaitu]

Added the functionality to send the articles that the user has seen before clicking on an article.

It updates the backend by using the logUserActivity function.

Added back the original message to LikeFeedbackBox with the original message and styling on it.

Regarding the texts, we have some suggestions, that we can talk about to our meeting on Monday :)

[oskaitu]

Combined LikeFeedbackBox and DifficultyFeedbackBox together within a "box" and added the text we talked about.

Added source prop to LikeFeedbackBox. UMR_SOURCE is sent from web and EXTENSION_SOURCE is sent from extension.

Made the information about the articles seen before a list instead of json format.

[oskaitu]

Have merged the updates from zeeguu/web into our branch. Have run the code and made appropriate changes to the functions we have added.

Not sure if relevant. But the way I was testing before was on the url: http://localhost:3000/render/read/article?id=206213 After merging changes from zeeguu/web I experience this error:

But it works fine when I use the url: http://localhost:3000/read/article?id=206213

Is it something I should look into, or should I just keep using the working path?

[oskaitu]

Elephant is back at his place now :)

[tfnribeiro]

Have merged the updates from zeeguu/web into our branch. Have run the code and made appropriate changes to the functions we have added.

Not sure if relevant. But the way I was testing before was on the url: http://localhost:3000/render/read/article?id=206213 After merging changes from zeeguu/web I experience this error:

But it works fine when I use the url: http://localhost:3000/read/article?id=206213

Is it something I should look into, or should I just keep using the working path?

This is because the scrollTop is an element that is rendered with the sidebar, so I wouldn't worry too much that it throws errors when used with the render. I will deploy an update so it doesn't throw errors to avoid it showing the error when you use the render view.

[mircealungu]

Nice! I've deployed the current version to zeeguu.org.

While testing it, I played a bit around with the look and the text and came up with this:

The difference with respect to the current solution are:

• instructions stand out less than the questions, so the learner can focus on the questions
• the instruction is directly expressed in terms of the benefits that the user gets, not in terms of zeeguu's benefits

For the first, the style changes are just use p instead of h3 and add some padding left/right:

If you like this, feel free to send a quick new PR and I'll merge it. Then we have to also release the browser extension, because many learners use that for reading!

P.S. Another variation of the text, might be: "Zeeguu will make better personalized recommendations if you provide feedback".