A browser extension is close to the page you are reading and the account already signed in on a publishing platform. The first is useful for capture. The second can help save drafts and needs clear confirmation.
DraPub handles capture and delivery separately. Selecting a destination workspace, checking content and confirming an account address different questions, even after the extension is connected to DraPub.
The extension captures accessible content from the page. Dynamic loading, authentication and media attachments can affect the result. Open the saved record in DraPub and check that it contains the body rather than only a title or navigation.
You can capture an authenticated page after opening it in your own browser session. This still does not guarantee complete processing of every video, attachment or hidden section. Keep the original URL for verification.
The extension uses the platform session in the browser. Platform credentials such as cookies and tokens stay there rather than being uploaded as content to DraPub Backend. DraPub and platform sign-in are separate, so check the platform account as well.
After reviewed content is handed off, confirm the target and action inside the extension. This places an account check close to the actual destination.
Adapters differ by platform: some use editors and others use platform interfaces. A directory entry does not establish identical format or media support. Read the current options and task result.
A background task can be interrupted, or the network can fail after a draft was saved. Missing a success response does not prove the destination received nothing. Check the draft box before retrying.
The extension also exports Markdown and images as a ZIP. Downloading those files completes export; uploading and arranging them remain separate. After a successful draft save, inspect its text and images before deciding to publish publicly.
See the Extension guide and Delivery results.
Q: Why does the extension ask for confirmation after DraPub review?
**A: ** The extension uses the current browser’s platform session. Confirming there lets you verify the account, content, and destination immediately before the operation.
Q: Are platform cookies uploaded with the content package?
**A: ** Platform credentials remain in the browser, and DraPub manages its own session separately. After connecting DraPub, still check sign-in on the destination platform.
Q: Why check the draft box after a timeout with no success message?
**A: ** The platform may have saved the content before the result failed to return. Check its draft box before retrying to avoid duplicate drafts.
