Description
The current Chrome Extension assumes it is interacting with a single-user backend. For the SaaS model, the extension must know who is using it so the backend knows which account to publish the blog to.
Expected Behavior
- Build a simple popup UI for the Chrome Extension with a "Log In" button.
- Implement a mechanism to store the user's session token/ID in Chrome's local storage after they log in.
- Update
content.js to append this user_id or token in the headers or body of the /generate-blog API request.
Description
The current Chrome Extension assumes it is interacting with a single-user backend. For the SaaS model, the extension must know who is using it so the backend knows which account to publish the blog to.
Expected Behavior
content.jsto append thisuser_idortokenin the headers or body of the/generate-blogAPI request.