Website
CoreInto can keep your public website as well as the portal. Pages are built from blocks, and plans, prices and domain prices come straight from your store, so the site never shows an old price. The site lives on your main domain (for example example.com) while the portal keeps its own address (for example my.example.com). Everything is in the same database, so a page changed in the admin area (or, later, in the mobile app) is changed everywhere.
The Website menu has five pages: Pages, Blog, Menus, Images and Website Settings.
Permissions#
| Permission | Allows |
|---|---|
Edit the website (website) | Pages, blog posts, menus and images |
Website settings (website.settings) | Website Settings, publishing as files, the zip download, and HTML blocks |
Staff without website.settings do not see or change HTML blocks. When they save a page that has one, it is kept exactly as it was.
Starting#
On a new installation, Website > Pages offers Make my site. It builds:
- a Home page: a large heading, three reasons to choose you, the plans of your first product group, a domain search and a closing button to the store;
- one page for each visible product group, with its plans;
- a Domains page with the search and a price table (when you sell domains);
- About us (left as a draft for your own words) and Contact us;
- the top and footer menus.
Everything it makes can be changed or deleted.
Pages and posts#
A page has a title, an address (/about-us/), a description for search engines and a list of blocks. Blog posts are the same, live under /blog/, and also have a date and an image. The blog list (/blog/) appears once a post is published.
Every page has two copies:
- the working copy, which you edit; and
- the published copy, which visitors see.
Save draft keeps your changes without touching the site. Save and preview opens the working copy as the site would show it, in a new tab; previews are never indexed by search engines. Save and publish puts the working copy on the site. A page with unpublished changes is marked "Changes not published" in the list. Unpublish takes a page off the site and keeps it as a draft.
The last 20 versions of each page are kept (each save, publish and restore). Earlier versions lists them; Bring back copies one into the working copy, and you publish it when ready.
The first page you publish becomes the home page, served at /. Choose another under Website Settings. The addresses blog, media, site-assets, admin, api and install are used by the site itself and cannot be page addresses.
Blocks#
The editor works without scripts: the arrows move a block, the copy button repeats it, the bin removes it, and Add a block adds one at the end. Blocks with a list (points, questions, figures, testimonials) have Add one and a remove button on each row.
| Block | What it shows |
|---|---|
| Hero | A large heading with text, up to two buttons and an image, on a light, dark or brand-coloured band |
| Text | A heading and Markdown text |
| Image and text | An image beside a heading, text and a button |
| Features | A grid of points with an icon, a title and a line each |
| Plans | The plans of a product group, with live prices, features (the lines of each product's description) and order buttons into the portal. One plan can be highlighted. |
| Domain search | A search box; the search runs in the portal's store |
| Domain prices | Register, transfer and renewal prices for the extensions you list, or for your spotlight extensions |
| Questions | Questions and answers; search engines can show them (FAQ structured data) |
| Call to action | A band with a heading, a line and a button |
| Numbers | A row of figures (years in business, customers…) |
| Testimonials | Words from your customers |
| Latest news | Your latest announcements |
| Latest posts | Your latest blog posts |
| Contact | Your address, phone and email from General Settings, with links to the contact form and a new ticket |
| HTML | Your own markup. Scripts do not run: the security policy blocks them. |
A link in a block or menu can be a page of the site (/about-us/), an anchor (#plans), a full address, mailto: or tel:, or a portal page written as portal:store, portal:domains, portal:client, portal:login, portal:register, portal:contact, portal:announcements, portal:knowledgebase or portal:cart. Portal links always go to the portal's address, however the site is served.
Prices in two currencies#
When currency by country is set up (Home country and World currency under the currency settings), price blocks carry both prices and the site shows a Prices for switch in the top bar. Visitors from your home country see the local currency first, others the world currency; the choice is remembered on their device. Plans show each plan's starting price, as the store does; Domain prices show the price for the shortest registration term.
Menus#
Website > Menus has the top menu and the footer menu. Each row has an order number, a label and a link; empty rows are left out. In the top menu, a row marked "Under the one above" opens from the item before it. Menus change on the site at once (no publishing needed).
Images#
Website > Images takes PNG, JPEG, GIF and WebP images up to 5 MB (SVG is not accepted, as it can carry scripts). Give each a description for screen readers and search engines. An image used by a page or as the logo cannot be deleted until it is taken out. Images are kept in the storage folder like other files; Storage Settings lists them as "Website images".
Website Settings#
| Setting | Meaning |
|---|---|
| The website is on | Off: the domain shows nothing from the site (the preview still works) |
| Domain | The address visitors type, with or without www. |
| How the site is served | From this CoreInto, or As files in a folder (below) |
| Folder | For files: the full path of the domain's web folder, outside CoreInto's own folder |
| Home page | The page served at / |
| Site name, Tagline, Logo | Shown in the top bar, the footer and search results |
| Main colour, Second colour | The theme's colours |
| Footer text | A line or two under the footer menu (Markdown) |
| Sign in and Order buttons | Buttons in the top bar that open the portal |
| Social media | Links shown in the footer |
From this CoreInto#
CoreInto answers requests for the site's domain itself, and pages are always current. The domain must reach the same hosting account and folder as CoreInto:
- on cPanel or intoPanel, add the main domain as an alias (parked domain) of the portal's domain; or
- point the main domain's document root to CoreInto's folder.
The portal must have its own address (a sub-domain such as my.example.com): the site's domain cannot be the portal's address. Pages are sent with a five-minute cache, and the site answers sitemap.xml and robots.txt on its own domain.
As files in a folder#
CoreInto writes the site as plain HTML files into the folder, for example the main domain's public_html, so the site stays fast and works even if the portal is busy. The "Publish the website as files" task writes it again every hour, so prices stay current; Publish now writes it at once. Only files CoreInto wrote are ever replaced or removed (it keeps a list in .coreinto-site.json). If the folder already has files of the same name, such as an old site's index.html, CoreInto stops and lists them; Move them and publish moves them into .coreinto-replaced/<date>/ in the same folder, never deleting them.
Hosted somewhere else#
Download the site as a zip gives the whole site as plain files to upload to any web host. Upload it again after changes.
Search engines#
Each page has its own title and description (or the page's description), a canonical address, Open Graph tags for links shared on social media, and structured data (the organisation on the home page, questions, blog posts). A page can be hidden from search engines, which also leaves it out of the sitemap. One address per page: /about-us is sent on to /about-us/, and the home page's own address is sent on to /.
Themes#
The look comes from website/themes/default/: layout.php, a file per block in blocks/, and assets/ (CSS and script). A theme folder with the same files can replace it. The website folder is never served to browsers (on nginx, add website to the rule that denies app and storage); its assets are served at /site-assets/.
Something missing? Ask in the community or open a ticket.