Guide / Getting Started with iBoard
KO EN

Getting Started with iBoard

Before using iBoard, it is important to understand how the system is structured and how each management area affects the website. iBoard is not only a page editor. It is a website management platform that combines pages, menus, boards, skins, media files, providers, templates, users, and optional shopping or billing features.

The most important rule is this: do not start by editing random pages. First understand the structure of the site, the role of Core Settings, and how pages are connected to menus and skins.

1. Understand What iBoard Manages

iBoard is designed to manage multiple parts of a website from one administrator system. Each menu controls a different part of the website or business operation.

Area What It Controls
Pages Website pages, page content, page registration, page layout connection, and file modification.
iBoard Board settings, board lists, board imports, core settings, and board-related pages.
Menu Website navigation menus and how visitors move between pages.
Media Images, documents, downloads, banners, and other uploaded files.
Site Site-wide settings, query tools, API generation, short codes, banners, themes, plugins, skins, SMTP, and app keys.
User Administrator and member accounts, profiles, and user roles.
Provider Email, SMS, communication providers, templates, message center, and send logs.
iShop Shopping features such as products, categories, collections, coupons, taxes, orders, and shipping scan.
Payment / Billing Payment transactions, payment providers, billing, recurring billing, customer billing, and payment logs.

2. Think of iBoard as a Structure, Not Just Screens

Many new users make the mistake of thinking that each screen works independently. In iBoard, most screens are connected.

For example, a public website page may depend on all of the following:

  • A registered page in Pages.
  • A layout or Core Page setting.
  • A skin or theme file.
  • Menu settings that link to the page.
  • Media files used inside the page.
  • Short codes, board settings, or dynamic content.
When something does not appear correctly on the website, check the full structure: page, menu, skin, media path, core setting, and permission.

3. Recommended Order for First-Time Setup

If you are setting up iBoard for the first time, follow this order. This reduces confusion and prevents unnecessary rework.

  1. Install iBoard and confirm that the Admin page opens correctly.
  2. Update the iKey immediately after installation.
  3. Review basic site information and server settings.
  4. Check the selected skin and understand how the layout is structured.
  5. Review Core Page Settings before editing individual pages.
  6. Upload or organize media files.
  7. Create or review pages.
  8. Connect pages to menus.
  9. Configure users and permissions.
  10. Configure communication providers such as SMTP or SendGrid if email sending is required.
  11. Test the website from the public side.
  12. Only then begin advanced features such as iShop, Payment, Billing, or Plugins.

4. Core Page Settings Are Important

Core Page Settings control shared layout areas such as Header, Top Area, Main Area, Bottom Area, Script, Style Sheet, and Night Mode.

Changes in Core Page Settings may affect many pages at the same time. This makes Core Page powerful, but also risky if changed without understanding.

Core Area Purpose
Header SEO tags, meta tags, page title, external CSS, and browser-related settings.
Top Area Common top layout such as logo, navigation, search, or header content.
Main Area The main page content area.
Bottom Area Footer, company information, policy links, and bottom layout.
Script Shared JavaScript used by the page or layout.
Style Sheet Shared CSS used by the page or layout.
Before editing Core Page Settings, copy the current code or create a backup. One small change can affect multiple pages.

5. Understand Save, Save to File, and Preview

iBoard may store content in the database, files, or both depending on the feature. Because of this, it is important to understand the difference between Save and Save to File.

Action Meaning
Save Saves the current setting or content to the database.
Save to File Writes the current code or content to a physical file.
Preview Opens a preview so you can check the result before applying it publicly.

If a change does not appear on the website, check whether the feature requires both database saving and file saving.

6. Plan Your Website Structure Before Creating Pages

Before creating many pages, decide how the website should be organized. A simple plan prevents duplicated pages, broken links, and confusing menus.

Recommended Planning Questions

  • What are the main sections of the website?
  • Which pages should appear in the top menu?
  • Which pages should be hidden or used only internally?
  • Which pages require login?
  • Which skin or layout should each page use?
  • Which images or files are required?
  • Who will manage each part of the website?

7. Media Paths Matter

Images and files are often used by pages, banners, products, templates, and custom HTML. If a file is moved, renamed, or deleted, any page using that file may break.

Use clear folders and simple file names. 

Recommended:
main-banner.jpg
about-company.webp
product-image-001.png
company-brochure.pdf

Avoid:
Final Image New Version!!!.jpg
image copy copy final.png
file name with many spaces.pdf
Before deleting or renaming media files, confirm that they are not being used by any page, banner, product, or template.

8. User Roles and Permissions Should Be Planned

Do not give every administrator full access unless it is necessary. iBoard includes user and role management so different people can manage different parts of the system.

User Type Recommended Access
Developer Core settings, files, scripts, styles, plugins, and advanced configuration.
Site Manager Pages, menus, media, banners, and general content.
Content Editor Page content, board content, images, and documents.
Shop Manager Products, categories, orders, coupons, tax, and shipping-related features.
Billing Manager Payment, billing, recurring payments, customer billing, and payment logs.

9. Email and Message Features Require Provider Setup

Features such as password reset, verification codes, newsletters, invoices, customer notices, and event-based notifications require a communication provider.

Before using these features, configure at least one active provider.

  • Use SMTP if you send email through your own mail server or hosting mail server.
  • Use SendGrid if you send email through SendGrid API.
  • Use Twilio or another SMS provider if SMS sending is required.
  • Always test the provider before using it in production.

10. Do Not Start Advanced Features Too Early

iShop, Payment, Billing, Plugins, API Generator, and Query Builder are powerful features. However, they should be configured after the basic website structure is stable.

Start with the foundation first:

  1. Site settings
  2. Core Page settings
  3. Pages
  4. Menus
  5. Media
  6. Users and permissions
  7. Communication provider

After these are stable, continue with shopping, payment, billing, or custom plugin features.

11. Common Mistakes to Avoid

Mistake Why It Causes Problems
Editing Core Page without backup It may break multiple pages at once.
Creating pages before planning menus The website structure becomes confusing.
Deleting media files too quickly Images or downloads may disappear from pages.
Activating providers without testing Email or SMS delivery may fail in production.
Giving full admin access to everyone Important settings may be changed accidentally.
Changing skins without checking layout differences Pages may look broken or inconsistent.

12. Recommended First-Day Checklist

  • Confirm that Admin login works.
  • Change the iKey after installation.
  • Review Site Management settings.
  • Confirm the selected skin.
  • Open Core Page Settings and understand the layout sections.
  • Upload only necessary media files first.
  • Create a small number of test pages.
  • Connect test pages to menus.
  • Create administrator users and assign proper roles.
  • Configure SMTP or SendGrid if email is required.
  • Preview and test from the public website side.

Final Recommendation

iBoard becomes easier to manage when you treat it as a structured platform rather than a simple page editor. Start slowly, understand how each part connects, and test each change before moving to the next step.

Build the foundation first. Once Site Settings, Core Page Settings, Pages, Menus, Media, Users, and Providers are stable, advanced features such as iShop, Payment, Billing, and Plugins will be much easier to manage.