Feature Requests
"What should we offer next?" Most websites guess. The feature request module asks: visitors propose ideas, others vote, and you see what people really want. I built it for ForgeCMS itself, and four of the first five requests were done within days. It works for bakeries too: which bread next, which workshop, which opening hours.
Goal
By the end of this chapter you can:
- run a voting page for ideas,
- moderate what appears,
- understand why one person cannot easily vote ten times.
Switching it on
Please add a wish list at /wishes where visitors can propose what we should
bake next and vote for it. I moderate (me@mybakery.com).
In app.sml:
Features {
admin: "me@mybakery.com"
Project { id: "bakery" title: "Our Bakery" page: "/wishes" }
}
On the page:
FeatureRequests { project: "bakery" }

A project is one list. You can have several: one for the shop, one for workshops. Each gets its own Project line and its own page.
The module needs mail on the server (chapter 10), because people log in by email.
How visitors use it
- They see the list of ideas, the most wanted at the top.
- To vote or to propose something, they log in: they enter their email address and get a link. One click, and they are in. No password, no account form.
- A vote is one click; another click takes it back.
- "Propose a feature" opens a short form: a title and a description.
Nobody sees who proposed or voted for what. The list shows only the ideas and the number of votes.
Moderating
New proposals wait for you (moderate is on by default). You get a mail with a link, look at the proposal, and approve, edit or delete it. Your own proposals appear at once.
Every request has a status you set: open, planned, in progress, done or rejected. Done and rejected ones move into a folded section below the list, so the list stays about what is still to do, and visitors see that wishes come true.
If someone misbehaves, you can block them. Their proposals disappear and their votes stop counting. Nothing is deleted; you can undo it.
Why votes are fair enough
One email address is one account, and one account has one vote per idea. The module also recognises the usual tricks: me+1@gmail.com and m.e@gmail.com are the same mailbox as me@gmail.com.
Someone with ten real mailboxes can still vote ten times. That is the honest limit of any voting without ID cards. For a list of ideas it is enough: you are not running an election, you are listening.
Pitfalls
- Login mails do not arrive: check spam, and the mail setup of chapter 10.
- A proposal does not appear: it waits for your approval.
- The page shows nothing: the
projecton the page must match anidinFeatures { }.
What you learned
Features { admin Project }switches the module on,FeatureRequests { project }shows a list.- Visitors log in with an emailed link, vote with one click, and propose ideas.
- You moderate, set the status of every idea, and can block misuse.
- One mailbox, one vote: fair enough for listening to your visitors.
