You have shipped a feature and your product is already on ShipFeed. Before sharing the announcement, it helps to know what the review covers, what you can check yourself, and what to do if a reviewer asks for a change.
When can I submit an update?
Your product needs approval before you can submit its updates. The product profile gives readers the context they need to understand your software. An update describes a particular launch, release, improvement, or milestone. If your product is still awaiting approval, start with the product submission checklist.
What does the review cover?
ShipFeed checks whether the update fits its publication guidelines. The submission should be about eligible software, describe genuine progress, and give readers enough information to understand what changed. Write the title and body in English, link to relevant destinations, and use material you have permission to publish.
You remain responsible for your description, product claims, supporting evidence, and publication rights. The ShipFeed terms explain the scope of editorial review and the publisher’s responsibilities.
What should I check before sending it?
- Name the product and the change early. A reader should be able to tell whether the update affects their work.
- Explain how people can use the change today. If it is in beta, available to selected users, or still rolling out, describe the current access conditions.
- Open each link as a reader would. Link to the relevant release notes, documentation, or product page and check the allowance shown in your workspace.
- Check that any screenshots and claims match the release you describe. If a number matters to the announcement, give the context needed to understand it.
For a starting structure, use the guide to writing a useful product update.
What does a specific update look like?
Consider a fictional release from MapleTasks. The team adds named column mappings for repeated CSV imports. Its update explains that a workspace admin can save a mapping after setting up an import, then select that mapping for the next file. The team names the accounts that can use it and links to instructions for setting up the mapping.
That gives readers a concrete change and a way to investigate it. A headline like “Our import experience is better” can become more useful simply by naming the workflow that changed and who can use it.
What should I do while the update is in review?
Check the article’s status in your ShipFeed workspace. Save the announcement URL for distribution once the article is published and opens for a signed-out reader. If your launch has a fixed date, give the review step time in your plan. ShipFeed’s terms say review priority may vary by plan, so use the actual publication status when coordinating the launch.
What if I’m asked to revise it?
- Read the reason and locate the part of the update it applies to.
- Address the underlying issue. Replace a broken link, explain who has access, or clarify the release detail that a reader could misunderstand.
- Check the saved status and follow the workspace’s submission controls to send the revised version for review.
If the note is unclear, contact support with the product name, article title, and the specific question you need answered. Keeping the revision focused makes it easier to explain what changed.