Test Purpose
This note records a test for the mobile blog publishing workflow. The goal is to let the app submit a publishing task, return control to the user quickly, and then check the task status in the background.
The publishing process is not instant. It may need to generate Markdown, upload assets, push changes to GitHub, trigger a Cloudflare build, and wait for the deployed URL to become available. If the app waits synchronously, the user interface can feel frozen or unreliable.
Queue and Polling Plan
Automated deployment takes 2-5 minutes.
I plan to check every 15 seconds to see if the release is successful.
The basic workflow is:
- The app creates a publishing task.
- The backend stores the task status as pending.
- The publishing worker handles the GitHub and deployment steps.
- The app polls the status endpoint every 15 seconds.
- When the status changes to success, the app can show the final blog URL.
SEO and Operations Value
This matters for SEO because failed or half-published posts can create broken links, missing images, or pages that exist in the sitemap before the actual HTML is ready. A queue-based workflow makes it easier to submit only completed URLs to Google Search Console, Bing Webmaster Tools, and IndexNow.
The next improvement is to store the build log, final URL, error message, and retry count for each task. That will make debugging easier when a post fails to publish from the mobile app.