Sections a small organization actually needs

A small publisher can describe the whole app in a short list. Adding sections because the builder’s gallery shows them is how the menu becomes a junk drawer.

A starting set

Section	What a visitor uses it for
Articles or notices	The thing that changed this week
About	Who runs this, and how to visit
Dates	What is on, with a date that can be corrected
Audio or a stream	Only if listening is the point of the visit
A saved list	So a visitor can return to one item
A way to reach you	A form or a plain address, not both hidden

What to leave out at first

Loyalty cards, chat, a second language, and a members’ area all sound serious. They also need a person. If you cannot name who answers the chat this month, do not turn the section on. An empty members’ area teaches people that the app is unfinished.

Count them against the plan

Write the six names down and ask which plan includes them without an extra fee. If the sixth item costs another slot, that fee belongs in the first-year budget, not in a surprise email. Native apps for the stores are a separate question from the section count. Settle the sections first. The store decision is easier once the list is short.