In the original Wapka, modules were everything. They gave users instant functionality — a guestbook, a forum, a chatroom — without touching code. That philosophy carried forward.
What’s built in
- Forum: threaded discussions, categories, moderation
- Chatroom: real-time text chat with user presence
- Gallery: image uploads, albums, lightbox viewing
- Guestbook: visitor comments with spam protection
- User system: registration, login, profiles, roles
- Blog: posts, categories, RSS, comments
- File manager: upload, organize, serve files
Every module works out of the box. Enable it, configure it, and it appears on your site. No plugin marketplace. No dependency hell. No “this module is incompatible with your theme.”
The community’s role
Modules evolve based on how people actually use them. A community member building a media site pushes the gallery module to handle more formats. Someone running a community forum surfaces edge cases in the moderation tools. Students using the blog module request features that make it into the next release.
The modules grow with the community. What started as simple WAP-era guestbooks evolved into modern commenting systems. What began as a basic file uploader became a storage layer serving terabytes.
Continue reading: The theming engine → The file manager that serves terabytes →