Pages
The Pages category is used to create, organize, configure, preview, copy, and delete website pages. It is one of the most important areas in iBoard because most visible website content is managed through pages.
Use this section when you need to create a new page, edit an existing page, connect a page to a layout, check the page URL, apply Core inheritance, preview the page, or manage page files.
Overview
A page in iBoard represents a website screen that visitors or members can access. Pages may be used for login, registration, search, profile, ranking, custom landing pages, company pages, service pages, product information pages, or any other website content.
The Pages section controls page records, layouts, addresses, Core inheritance, iBoard usage, and quick management actions.
| Menu | Main Purpose |
|---|---|
| List | View and manage all registered pages. |
| Register | Create a new page. |
| Setting Core | Manage Page Core settings used by normal website pages. |
| Modify Files | Open the file editor for editing page-related files. |
Page List
The Page List displays registered pages in the system. Pages are usually grouped by page group, such as Basic or No Group. Each row shows page information and quick action buttons.
| Column | Description |
|---|---|
| No. | The internal page number or page ID. |
| Page Name | The name of the page. This is used to identify the page in the administrator system. |
| Layout | The layout or skin used by the page. This affects how the page is displayed. |
| Address | The public or internal URL used to open the page. |
| Core | Shows whether the page inherits Core settings or uses its own page-level configuration. |
| iBoard | Indicates whether the page is connected to an iBoard function or board-related page. |
| Actions | Provides page management actions such as Setting, Page View, Copy, and Delete. |
Page Groups
Pages may be grouped for easier management. In the list screen, groups such as Basic or No Group can be expanded or collapsed.
- Basic: Common system pages such as Login, Register, Search, Profile, Ranking, and related pages.
- No Group: Pages that are not assigned to a specific group.
- Custom Groups: Additional groups can be used to organize project-specific pages.
Action Buttons
| Button | Description |
|---|---|
| Create Page | Creates a new page record. |
| Core Setting | Opens Page Core settings for managing shared page layout sections. |
| Setting | Opens the selected page�s settings editor. |
| Page View | Opens the selected page for preview or public viewing. |
| Copy | Copies the selected page and its basic configuration. |
| Delete | Deletes the selected page. Use carefully. |
Address
The Address column shows the URL used to open a page. For example:
/iPage?ipage=9
This address can be used in menus, buttons, links, or redirects. If a page does not open correctly, confirm that the page ID and address are correct.
Core Inheritance
The Core column shows whether a page inherits settings from the Page Core. When a page is marked as inherited, it uses shared Core layout sections instead of only page-specific layout.
Core inheritance is useful when many pages should use the same header, top area, bottom area, script, style, or common layout structure.
Page Core is for normal website pages. It is different from iBoard Core, which is used for board pages.
Relationship with Other iBoard Areas
| Related Area | Relationship |
|---|---|
| Menu | Pages can be linked from website menus. |
| Page Core | Pages may inherit shared page layout sections from Core Settings. |
| Skin / Layout | The selected layout controls how the page appears visually. |
| Media | Pages may use uploaded images, documents, and media paths. |
| iBoard | Pages can contain iBoard shortcodes or connect to board-related functions. |
| Modify Files | Page-related files can be edited through the file editor when needed. |
Recommended Workflow
- Plan the page purpose before creating it.
- Open Admin > Pages > List.
- Click Create Page or select an existing page.
- Choose the correct layout or skin.
- Decide whether the page should inherit Core settings.
- Configure page content and settings.
- Save the page.
- Use Page View to preview the result.
- If the page should be public, connect it to the Menu.
- Test the page from the public website side.
Common Use Cases
| Goal | Recommended Action |
|---|---|
| Create a new landing page | Use Create Page, select a layout, add content, and preview the page. |
| Edit an existing page | Click Setting on the target page row. |
| Open a page directly | Use Page View or copy the address from the Address column. |
| Reuse an existing page structure | Use Copy, then edit the copied page. |
| Apply a shared header or footer | Use Core Setting and enable Core inheritance for the page. |
| Remove an unused page | Use Delete only after confirming it is not linked from menus or other pages. |
Important Notes
- Do not delete a page unless you are sure it is no longer used.
- Check whether a page is connected to a menu before deleting it.
- Changing a layout can change the visual structure of the page.
- Core inheritance can affect how shared header, footer, script, and style areas are applied.
- Page addresses may be used in menus, buttons, emails, and external links.
- After copying a page, update the copied page name, address, and content as needed.
Troubleshooting
| Problem | Possible Cause | Solution |
|---|---|---|
| Page does not open | The page ID may be wrong, the page may be deleted, or the address may be incorrect. | Check the Address column and confirm the page exists. |
| Page design looks wrong | The wrong layout or skin may be selected. | Open Setting and check the layout selection. |
| Header or footer is missing | Core inheritance may not be configured correctly. | Check Page Core settings and the page�s Core option. |
| Page is not visible in the menu | The page may not be connected to a menu item. | Open Menu settings and link the page address. |
| Copied page shows old content | The copied page may still contain original page content or settings. | Edit the copied page and update all necessary fields. |
Best Practices
- Use clear page names.
- Group pages logically when possible.
- Use Core inheritance for pages that share the same structure.
- Preview every page after editing.
- Check mobile layout if the page is public.
- Keep important page addresses documented.
- Before deleting a page, check menus and links that may reference it.
Pages are the visible structure of the website. Plan page names, layouts, addresses, and Core inheritance carefully before building many pages.