Pikipedia:Pikmin Bloom update procedure

Documenting Pikmin Bloom on Pikipedia requires active maintenance, because its features often change due to updates, events, and other occurrences. This procedure explains what to do whenever there's an event, update, or some other change or announcement, in order to keep the wiki accurate.

When there's an update

Whenever there's a software update to the game:

• Check the App Store page, Google Play page, and official update forum, and see what they say about the update.
• Create a new row in the table in the update article, and copy the official update logs into that table, changing them in order to fit with the wiki's style (i.e. adding links, rewording to avoid using "you", etc.).
• Install the update when you're sure that there isn't anything that needs testing before and after the update.
• See if there are any changes which haven't been documented, and see if people on the internet have found any other undocumented changes. Document those when it's practical to.
• Go to the articles about topics affected by the update. If the change was substantial enough to affect the content of the page, edit the page to reflect the current state of things, and add a row to the History section to explain what changed in the update. If documenting the changes requires further testing, place the {{update}} template in the relevant section so someone can do it later.

When a Community Day is announced

When the next Community Day event is announced in the in-app news feed or elsewhere:

• Read the details of the event.
• Go to the event article. Copy and paste the previous Community Day section into a new section, and change the date, tense, and details as necessary. This is useful to ensure consistency in wording.
• Upload a promotional image for the event and add it to the article, making sure that images alternate between left and right.

When another type of event is announced

When an event is announced that's not a Community Day:

• Read the details of the event.
• Document it on the event article in a way that's similar in style to the other events.
• Upload a promotional image for the event and add it to the article, making sure that images alternate between left and right.

When an event starts

When an event has started in most timezones:

• Reword the event's description in the event article to be in present tense.
• Go to the articles of any topic affected by the event, and edit them to reflect the temporary changes, adding a row in the History section.

When an event finishes

When an event is over in most timezones:

• Reword the event's description in the event article to be in past tense.
• If there were any unannounced features of the event, document those.
• Go to the articles of any topic affected by the event, and edit them to reflect things returning to normal, adding a row in the History section.

When there's a new type of flower

When a new type of flower is added to the game:

• Go to the Pikmin Bloom article and document the new flower type in the Flowers section.
• Go to the nectar, petal, and flower planting articles and add the new flower type to the table.
• When images of the new flower type are available, upload those using the file names that will cause them to appear in the other articles.

When flower availabilities change

Whenever the flowers available from Big Flowers or challenges change:

• Go to the Big Flower article and describe what's changed in the table, making the wording similar to what's already there.
• Go to the challenge article and document the new nectar rewards in table format, and move the old rewards to the History section in text format.

When there's a change of items in the shop

Whenever the items in the shop change:

• Go to the shop article and document the changes. Move any items that are no longer available to the formerly available items section, and document any new items.

When any other announcement happens

When there's any other official announcement about the game:

• Go to the articles relevant to the announcement and change them as necessary, making sure to document changes in the History section if necessary.