Goal of Rendering

  • For SEO optimization
  • Improve page access performance

Idea of Rendering: Static + Dynamic

  • Static Parts: home page, all articles, sitemap
  • Dynamic Parts: category, tags, search, comment, star, view stat, etc.

Achieve the organic balance between SEO optimization and system flexibility through static + dynamic mechanism

Timing of Rendering

To balance rendering performance, two timings of rendering are provided: site wholly building and article separately rendering

Site Wholly Building

In the page Settings-CMS, click the button Build to render and output all files in the site one-time

What situation needs to perform Site Wholly Building?

  • Any change which may affect the overall effect of site, such as category tree change, configuration change, etc.

Ariticle Separately Rendering

When an article is published, the article and home page are rendered in real time

SEO Optimization

There are three SEO files: robots.txt, sitemapindex.xml and sitemap.xml.

SEO files are all output at one time during site wholly building, and automatically updated when article separately rendering

Category, Tag, Search

There is no need to render the article list of category, tag, search, etc., since the site map file is used and all articles have been rendered as static files. We could just perform the backend API through ajax when need to get the article list

CMS, Theme, Plugin

The module a-cms only provides the basic rendering mechanism and rendering skeleton. The specific page layout, elements, and functions are implemented by a combination of themes and plugins. This mode enables us for rapid deployment and fully releases the scalability and flexibility of CMS

You can freely combine themes and plugins, and even implement your own themes and plugins to present completely different site effects

Ecology and Contribution

Hope you can join the ecology of CabloyJS to share your wisdom and achievements