frontity.settings.jsfile. Let's take a look at each concept you need to understand in order to use it properly.
matchsetting. Each time a new request is received by Frontity, it tests the URL against the
matchfield to know which site it should load:
"site-1"settings are loaded and if the URL is
"site-2"settings are loaded.
/blogfolder below the main domain
?frontity_name=query, which should match the
namespecified for your site. For example, using the
frontity.settings.jsfile above, to access
site-2, you should use:
activeprop. That means you can deactivate a package without having to delete it from your settings file.
settingsof a Frontity project are written in the
stateas the database of your application. And if you come from a React background, well... it's the
statethat you usually find in Redux or MobX. That
stateis accessible by your packages at runtime.
wp-sourcepackage uses the
sourcenamespace to store its settings. And our
tiny-routerpackage uses the
frontitythat is the place to set the general properties of our site. There's a mandatory property we need to set under the
stateof Frontity. Most of the time you will use this to configure the settings of each package.