AppWise CMS Official Documentation v1.0 · Updated: July 9, 2026
TR EN DE RU AppWise Labs
AppWise CMS

Manage content, design, SEO and operations from one panel.

AppWise CMS is a modular management panel for corporate websites, catalogs, product pages, media files, multilingual content, forms and analytics workflows.

Quick Start Content Management
Panel scope Pages, products, menus, media, SEO, languages, users and backups
Purpose Manage daily website operations without relying on a technical team
Recommended flow Settings → Content → Menu → SEO → Launch check
Content Pages, articles, products, menus
Design Theme, builder, header, footer
Operations Forms, modules, visitor analytics
Administration Languages, users, logs, backups

Quick Start

For a new website setup, complete the basic settings first, then create the content and menu structure.

  1. Enter company name, URL, contact details and the global SEO title in Site Settings.
  2. Upload brand assets in Logo and Favicon.
  3. Check theme, header, footer, color palette and font settings in Design.
  4. Set active languages and the default language in Languages / Translation.
  5. Create main pages and category structures in Page Management.
  6. Connect pages, product categories or custom links from the Menu section.
  7. Review sitemap, robots and redirects in SEO Tools.
Tip: Before publishing, check slug, meta title and meta description for every active language.

Panel Interface

The admin panel consists of the sidebar, top bar and main workspace. Use sidebar search to quickly reach modules.

  • Sidebar: Main modules and submodules.
  • Top bar: Site shortcut, language selection, user actions and quick access.
  • Workspace: Lists, forms, modals and builder screens.
  • Permissions: Menus and actions may be hidden depending on the user role.
Note: Users without permission may not see some menus or perform save/delete actions.

Page Management

Page Management is used for corporate pages, content pages, landing pages and builder-based custom pages.

New page workflow

  1. Create a category from Page Categories if needed.
  2. Open the page form from Page Management → Add New.
  3. Choose the content mode: classic editor or builder mode.
  4. Fill page name, slug and content fields for every active language.
  5. Complete SEO title, meta description, keywords and tags.
  6. Configure image, icon, gallery or comment options if needed.
  7. After saving, connect the page to navigation from the Menu section.

Key fields

  • Page name, subtitle, content and video fields
  • Language-based slug and SEO fields
  • Featured image, icon and image size options
  • Gallery, comments, FAQ and team visibility
  • Classic content or builder content mode

Builder mode

Builder mode lets you create a page using sections, columns and elements instead of a single rich text area.

Screenshot suggestionPage list, new page form, SEO preview and builder editor screen.

Article Management

Article Management is used for blogs, news, announcements or knowledge base content.

  • Article categories can be created.
  • Each article has language-based slug and SEO fields.
  • Sidebar position can be right, left or disabled.
  • Featured image and listing layout can be adjusted.
Best practice: Keep article titles short and write descriptions that read well in search results.

Product Management

Product Management is used for product catalogs, service listings and inquiry-based product pages.

Product publishing workflow

  1. Create the category tree under Product Categories.
  2. Create a product from Product Management → Add New.
  3. Assign the product to the correct category.
  4. Fill product name, short description and detailed content in required languages.
  5. Add product image, gallery and catalog/file links if available.
  6. Create extra tabs for technical information, tables or documents if needed.
  7. Fill SEO fields and test the frontend link.

Product categories

Categories are hierarchical. Root category, child category and product sidebar behavior work together.

Product fields

  • Product name, slug, description and short description
  • Product image and gallery
  • File links
  • Extra tabs
  • SEO title, description, keywords and tags
  • Request form integration
Note: Check category selection and sidebar root settings so the product appears in the correct sidebar tree.
Screenshot suggestionProduct list, product form, category tree, sidebar settings and frontend product detail page.

Gallery and Files

Media management consists of image galleries and downloadable/manageable files.

  • Gallery: Connect image lists to content or modules.
  • Files: Manage PDFs, catalogs, technical documents and similar files.
  • Images can be used in content, products, galleries or builder elements.
Note: Very large images slow down pages. Use web-optimized images.

Theme and Appearance

The Design section controls the website appearance: theme, header, footer, color palette, fonts and custom CSS.

Recommended design setup order

  1. Select the active theme first.
  2. Upload logo and favicon assets.
  3. Check header background, light/dark logo and menu behavior.
  4. Set primary color, footer color, breadcrumb color and text color.
  5. Configure footer columns and widget content.
  6. Check mobile appearance separately.
  • Theme selection
  • Header background, logo selection and form shortcuts
  • Primary, footer, breadcrumb and body text colors
  • Body font selection
  • Custom CSS area
Best practice: After changing the theme, check home, product detail, category and contact pages together.

Builder Structure

AppWise CMS includes Home Builder, Page Builder and Contact Builder. Builder is used to manage pages as blocks.

How builder works

  1. Section is a horizontal page area.
  2. Column defines the column structure inside a section.
  3. Element is the content component placed inside a column.
  4. Each element may have its own content, image, link and language fields.
  5. Frontend order follows the order set in the builder.

Standard elements

BannerRich TextAccordionLogo SliderStatsTeamTestimonialsPricingTimelineHTML BlockDividerTabbed ContentVideoRequest FormImage

Themes can define their own extra elements, so available elements may vary by active theme.

Note: HTML Block is powerful but should be used carefully. Invalid HTML can break page layout.
Screenshot suggestionHome Builder element list, Page Builder section/column structure and element edit modal.

Forms and Applications

Forms and Applications is used to manage records submitted by visitors.

  • Contact form
  • Human resources form
  • Quote form
  • Order form
  • Product / service request form

Form records can be tracked by read status. Some forms may not appear if related modules are inactive.

Modules

The module system is used to enable or disable CMS features and manage page/plugin type structures.

Example modules

HomeProductsContactFAQReferencesOur TeamPricingQuoteOrderHuman ResourcesWorking HoursRequest Form
Note: Required modules are necessary for the system and should not be removed.

SEO and Webmaster

SEO tools manage search visibility and technical redirects.

SEO check flow

  1. Use a unique slug for every page, product and article.
  2. Write short and meaningful meta titles.
  3. Write meta descriptions that summarize the actual page content.
  4. If a URL changes, redirect the old URL to the new one.
  5. Check sitemap and robots.txt before launch.
  6. Verify Google Analytics and Search Console codes.
  • Google Analytics settings
  • Google Search Console settings
  • Sitemap management
  • Robots.txt management
  • RSS settings
  • Redirect management
  • Slug / link management
  • Failed URLs and failed login records
  • Cache clearing
Tip: After URL changes, redirect old links to new links from Redirect Management.

Visitor Analytics

Visitor Analytics helps you view daily visitor activity and popular pages.

  • Daily visitors
  • Visitor details
  • Popular pages

These reports help understand which content receives more interest and guide content strategy.

Languages and Translation

Language management controls frontend content and panel language. Active languages, default language and language ordering are managed here.

New language workflow

  1. Open Languages / Translation → Language Management.
  2. Choose the language from inactive languages.
  3. Activate the language and set its order.
  4. Change default language if needed.
  5. Fill pages, products, menus, modules and footer content for the new language.
  6. Check language order and active language on the frontend.
  • Active / inactive language management
  • Default language selection
  • Language order
  • Panel translations
  • Content translation synchronization
Note: After adding a new language, page, product, menu and module content must be filled for that language.

Users and Permissions

Users section manages admin accounts, panel language and permissions.

  • Super Admin: Has all permissions.
  • Admin: Works with module-based permissions.
  • Permissions are divided into actions such as view, create, edit and delete.
  • Panel language can be assigned to each user.
Best practice: Give daily content editors access only to the modules they need.

Backups

The Backup section is used for database, file and system-level backup operations.

  • Database backup
  • File backup
  • System backup
  • Migration backup
  • Storage cleanup
  • Owner log records
Note: Before major updates, take both database and file backups.

Launch Checklist

Use this checklist before launching a new website or a major content update.

Tip: Use this list as part of the client delivery process for every project.

FAQ

My page does not appear in the menu. What should I do?

Creating a page does not automatically add it to navigation. Add the related page as a menu item from the Menu section.

I added a language but content appears empty.

Translation rows are created when a new language is added, but content text must be filled manually.

The product sidebar opens incorrectly.

Check the product category and product/module sidebar settings. Use sidebar root setting if needed.

When should sitemap be updated?

Check sitemap whenever a new page, product, category or module page is published.

A builder element is not visible on the frontend.

Make sure the element is active, supported by the selected theme and its content fields are filled.