Next.js does not provide a blog database or CMS on its own. Your developer connects Spron to the place where your articles and images are stored.
What your developer sets up
- A public HTTPS receiver in your Next.js app.
- A saveArticle function that creates or updates a post using the Spron article ID.
- A saveImage function that uploads images to permanent storage.
- Cache updates so the blog list and article page show the saved version.
Spron's Next.js connection screen includes an App Router example. Its storage functions must be implemented for your project before it can save real articles.
Connect the receiver
- Ask your developer to deploy the receiver.
- In Spron, open Integrations → Next.js → Connection.
- Enter the public receiver address and connect it as an owner or admin.
- Copy the token shown once and give it to your developer through a private channel.
- On the server, use that value for SPRON_ACCESS_TOKEN and SPRON_WEBHOOK_SECRET.
Keep these values in server environment variables. Do not use NEXT_PUBLIC_ variables for them.
Match the content
The receiver gets the standard Spron article fields. Your developer maps the title, HTML body, description and permanent image URLs into your content store. Use article.id as the stable post key.
The receiver should return published_url only after the page is public. If it saves a draft, it should return the external post ID without a public URL.
Check the result
Send one ready article. Check its saved record, public page, images and cache. Republish it and confirm that the same post updates.
For a Git or MDX blog, your developer must also provide the file-saving and build process. Spron does not commit files or deploy your Next.js site for you.