npx frontity create <project-name>
and you'll get a project with the same structure as the one explained in this guide.package.json
file where the dependencies needed for your app to work are declared.frontity.settings.js
file where the basic setup for your app is already populated.packages
folder with mars-theme
installed inside.package.json
filefrontity
: this is the main package, where we can find all the methods we might need to use during development. It's also where the CLI lives.@frontity/core
: here is where the magic happens. Core takes care of all the bundling, rendering, merging, transpiling, serving, etc. We don't need to access to it in order to develop a Frontity app.@frontity/wp-source
: this package is the one that connects to the WordPress REST API of your site and fetches all the data needed on your Frontity theme.@frontity/tiny-router
: this is a small package that handles window.history
and helps us with the routing on mars-theme
.@frontity/mars-theme
: this is our starter theme, where we build our site with React.mars-theme
dependency has no version but a path. This is how we need to add our custom packages (those we are developing inside the app) to our package.json
so they will be treated as if they were living in node_modules
.frontity.settings.js
filepackages
foldermars-theme
. Any changes done in these extensions during development will refresh our site automatically.frontity
, all the packages defined in frontity.settings.js
are imported by @frontity/file-settings
and the settings and exports from each package are merged by @frontity/core
into a single store
where you can access the state
and actions
of the different packages during development using @frontity/connect
(our state manager).