Guide / Core Page Settings
KO EN

Core Page Settings

Core Page Settings are used to manage shared layout sections, header code, scripts, styles, and night mode settings for normal website pages. This Core is for general pages, not for iBoard board layouts.

Use Core Page Settings when multiple pages should share the same header, top area, footer, script, stylesheet, or overall layout structure.

Overview

A Core Page works as a reusable base layout for website pages. Instead of editing the same header, footer, CSS, or script on every page, administrators can define common areas once and let pages inherit them.

Core Type Purpose
Page Core Controls shared layout sections for normal website pages.
iBoard Core Controls shared layout sections for iBoard board pages.

When to Use Core Page Settings

  • When many pages should use the same header or footer.
  • When you want to manage SEO meta tags in one shared layout.
  • When pages should share the same top, left, right, or bottom layout areas.
  • When you want to apply common CSS to a group of pages.
  • When you want to apply common JavaScript to pages using this Core.
  • When you want to manage night mode styles for pages.
  • When you want to export the Core layout to files using Save to File.

Core Page Settings Area

The top section defines the basic Core Page information.

Field Description
Core Page Name The name used to identify this Core Page. Example: AIZAAC.
Require Login Requires users to sign in before accessing pages that use this Core Page.
Select Skin Selects the skin or theme connected to this Core Page.

Code Editor

The Code Editor contains the shared layout and resource sections used by pages. Each tab controls a different part of the page structure.

Tab Purpose Recommended Use
Header Controls the page <head> area. Use for meta tags, SEO title, description, canonical URL, Open Graph tags, favicon, external CSS links, and browser settings.
Top Area Content displayed at the top of pages. Use for site header, logo, navigation, search, language selector, or hero sections.
Left Area Left-side layout area. Use for left navigation, filters, categories, or sidebar content.
Main Area Main page content area. Use for the main page body or page placeholder content.
Right Area Right-side layout area. Use for right banners, related links, recommended content, or side panels.
Bottom Area Content displayed at the bottom of pages. Use for footer, copyright, contact information, policy links, or bottom navigation.
Script Shared JavaScript for pages using this Core. Use for common page behavior such as menus, popups, scroll effects, or UI interactions.
Style Sheet Shared CSS for pages using this Core. Use for common page layout, typography, colors, buttons, cards, and responsive styles.
Night Mode Dark mode or night mode styling. Use for dark backgrounds, light text, border colors, and night mode component styles.

Header Tab

The Header tab is one of the most important sections because it affects SEO, browser behavior, social sharing, and external resource loading.

Common Header Content

<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">

<title>AIZaac - No-Code Website Management Platform</title>

<meta name="description" content="AIZaac is an easy and powerful no-code website management platform.">
<meta name="keywords" content="AIZaac, website builder, website management, iBoard">
<meta name="robots" content="index, follow">

<link rel="canonical" href="https://your-domain.com/">

Open Graph Example

<meta property="og:type" content="website">
<meta property="og:title" content="Your Site Title">
<meta property="og:description" content="Your site description.">
<meta property="og:url" content="https://your-domain.com/">
<meta property="og:image" content="https://your-domain.com/images/share.jpg">
Header values should match the actual website domain, page purpose, and sharing image path.

Use Default Header

The Use Default Header button can insert a default header structure. This is useful when creating a new Core Page or restoring standard meta tags.

  • Use it when the Header tab is empty.
  • Use it when you want to start from a standard SEO header.
  • Use it carefully because it may replace existing header code.
Before using Use Default Header, copy your current Header code if it contains custom SEO tags or scripts.

Top, Left, Main, Right, and Bottom Areas

These tabs control the structural layout areas of pages that use this Core. The actual output depends on the selected layout and skin.

Top Area Example

<header class="site-header">
    <div class="site-logo">AIZaac</div>
    <nav class="site-nav">
        <a href="/">Home</a>
        <a href="/about-us">About</a>
        <a href="/contact-us">Contact</a>
    </nav>
</header>

Bottom Area Example

<footer class="site-footer">
    <p>� 2026 AIZaac. All rights reserved.</p>
</footer>

Script Tab

The Script tab is used for JavaScript that should apply to all pages using this Core.

document.addEventListener("DOMContentLoaded", function () {
    console.log("Core page script loaded.");
});
Scripts added here may run on every page using this Core. Avoid placing page-specific scripts here unless all pages need them.

Style Sheet Tab

The Style Sheet tab is used for CSS shared by pages using this Core.

.site-header {
    display: flex;
    align-items: center;
    justify-content: space-between;
    padding: 20px 32px;
}

.site-footer {
    padding: 30px;
    text-align: center;
    border-top: 1px solid #e5e7eb;
}

Night Mode Tab

Night Mode is used to define dark mode styles for pages using this Core.

body.night-mode {
    background: #0f172a;
    color: #f8fafc;
}

body.night-mode .site-header {
    background: #111827;
    border-bottom: 1px solid #334155;
}

Save, Save to File, and Preview

Button Description
Save Saves the Core Page settings to the database.
Save to File Writes the Core Page code to physical files when file-based output is required.
Preview Opens a preview so you can check the result before applying it publicly.
List Returns to the Core Page list.
Create SQL Generates SQL for backup, migration, or deployment.
Save and Save to File are different. Save stores settings in the database. Save to File writes code to actual files.

Recommended Workflow

  1. Open Admin > Pages > Core Setting.
  2. Enter or confirm the Core Page Name.
  3. Decide whether Require Login should be enabled.
  4. Select a skin if needed.
  5. Edit the Header first, including SEO and meta tags.
  6. Edit Top, Main, Left, Right, and Bottom areas as needed.
  7. Add shared CSS in Style Sheet.
  8. Add shared JavaScript in Script only when needed.
  9. Add Night Mode styles if the site supports dark mode.
  10. Click Save.
  11. Use Preview to check the output.
  12. Use Save to File if the deployment requires file output.

Common Use Cases

Goal Recommended Section
Add shared SEO tags Header
Add the same header menu to many pages Top Area
Add a shared footer Bottom Area
Add a left navigation area Left Area
Add common page styling Style Sheet
Add common page JavaScript Script
Add dark mode support Night Mode

Important Notes

  • This Core is for normal website pages, not iBoard board pages.
  • Changes may affect every page using this Core.
  • Always back up Header, Script, and Style Sheet code before major changes.
  • SEO values should match the real website domain.
  • Do not place page-specific code in the Core unless all pages need it.
  • After saving, preview pages that inherit this Core.
  • If the website uses file-based output, use Save to File after saving.

Troubleshooting

Problem Possible Cause Solution
Changes do not appear The page may not inherit this Core, or Save to File may be required. Check the page Core setting and use Save to File if needed.
Header meta tags are wrong The Header tab may contain old SEO values. Update title, description, canonical URL, and Open Graph values.
Script breaks multiple pages A shared script error affects all pages using this Core. Check the browser console and fix or remove the script.
CSS affects too many elements CSS selectors may be too broad. Use specific wrapper classes and scoped selectors.
Preview looks different from live page Cache, file output, skin selection, or page inheritance may differ. Clear cache, confirm selected skin, and check Save to File requirements.

Best Practices

  • Use Core Page Settings for shared page structure only.
  • Keep Header focused on SEO and external resources.
  • Keep HTML in layout areas, CSS in Style Sheet, and JavaScript in Script.
  • Use clear class names to avoid conflicts with page-specific content.
  • Preview before applying changes to production pages.
  • Use Create SQL or copy code before making large changes.
  • Separate Page Core and iBoard Core responsibilities clearly.
Core Page Settings make it easier to maintain a consistent website layout. Use it for shared page-level structure, but remember that changes may affect many pages at once.