Overview
Wapka offers three ways to build a site. This guide helps you pick the right one. You can switch engines later from your site settings, so you are never locked in.
TAG (static pages)
Best for: portfolios, landing pages, simple HTML sites
TAG is Wapka original static page builder. You write HTML, CSS, and JavaScript directly. There is no server-side processing — what you write is what gets served.
When to choose TAG
- You want a fast, simple site with no backend
- You are comfortable writing HTML and CSS by hand
- You do not need user accounts, forms, or dynamic content
How it works
- Create a site and select TAG engine
- Go to Pages and create HTML pages
- Or upload HTML/CSS/JS files through the File Manager
- Your site is live instantly
Limitations
- No server-side scripting
- No database access
- Forms need external services (like Formspree)
![TAG engine site overview showing the Pages section]
Lua Framework
Best for: APIs, dynamic web apps, custom logic
Lua is a modern server-side runtime built into Wapka. You write Lua scripts that handle HTTP requests, query the database, and render HTML. It is as powerful as Node.js or PHP but simpler to learn.
When to choose Lua
- You need a backend (user accounts, forms, database)
- You want to build a REST API
- You need custom routing and middleware
- You want full control over every request
How it works
- Create a site and select Lua engine
- Open Code Studio and write your init script
- Define routes, handlers, and database queries
- Your app runs server-side on every request
local app = framework()
app:get("/", function(ctx)
return { message = "Hello from Wapka Lua!" }
end)
What you get
- URL routing with parameters and wildcards
- Middleware for auth, logging, and CORS
- Built-in Dataset (NoSQL database)
- Smarty template rendering
- REST API endpoints automatically
![Lua Code Studio showing a simple route handler]
Native App
Best for: blog, forum, store — ready-made solutions
Native Apps are pre-built applications you install with one click. They include database schemas, admin panels, and frontend templates. You customize them through settings, not code.
When to choose Native App
- You want a blog, forum, or store without writing code
- You need features fast (comments, categories, moderation)
- You prefer configuration over customization
How it works
- Create a site and select Native App engine
- Choose an app (blog, forum, store)
- Install it — the database and pages are created automatically
- Customize settings, upload a logo, and start publishing
Available apps
| App | Features |
|---|---|
| Blog | Posts, categories, comments, RSS |
| Forum | Boards, threads, replies, moderation |
| Store | Products, cart, checkout (coming soon) |
![Native App installation screen showing available apps]
Comparison
| Feature | TAG | Lua | Native App |
|---|---|---|---|
| Code required | HTML/CSS/JS | Lua + HTML | None |
| Database | No | Yes (Dataset) | Yes (auto) |
| REST API | No | Yes | Limited |
| Custom routing | No | Yes | No |
| Best for | Static sites | Dynamic apps | Ready-made solutions |
| Switchable later | Yes | Yes | Yes |
Still not sure?
- Just want a simple page? → Start with TAG
- Want to build an app or API? → Start with Lua
- Want a blog or forum today? → Start with Native App
Next: Follow the Quickstart to create your first site.