The lifecycle of Phenomic is pretty light and can be summarized like this:
- Initialisation from configuration,
- Content API initialisation from transformed content files (optional),
- Rendering via a development server or static rendering as files for production.
What’s cool about Phenomic is that the entire lifecycle is configurable via plugins.
Relying on existing plugins is a good first step to get started with Phenomic. Even better, you can directly choose a preset to start using it in seconds. And if you don’t find something that fit your needs or just miss something, your can make your own plugin.
Phenomic took inspiration from metalsmith by choosing to have a very light core highly extensible with plugins.
Plugins can interact at all stage of Phenomic process (during both development or static generation). A plugin can do multiple things but generally you will find this 4 types of plugins.
This will handle the generation of the html/dom (static/client side). That’s probably the most important type of plugins. Depending of the renderer plugin you will choose, this might completely change your experience with Phenomic.
Example: React (@phenomic/plugin-renderer-react)
Example: Webpack (@phenomic/plugin-bundler-webpack)
This will handle the transformation of files found by phenomic. Optional if you directly hit an existing API.
Example: Markdown (@phenomic/plugin-transformer-markdown) or JSON (@phenomic/plugin-transformer-json)_.
Other kind of plugins
You will also find some various kind of plugins that can do some other stuffs like generating an RSS feed from your content files or just serve static files from a
/public folder (eg:
robots.txt and friends).
Presets are a collection of plugins. For now we have only one, but we want more.
That’s the fastest way to start with Phenomic. You can directly check out existing tutorials