Development Workflow

Once Genix has been installed, the primary command used during development is genix watch. This command launches a lightweight HTTP server and enables live reload functionality, streamlining the feedback loop while you build your site.

Local HTTP Server

When running genix watch, Genix serves your site through localhost on a specified port. The server displays the contents of the distribution directory, making it easy to verify that absolute URLs and internal links resolve correctly before deploying to production.

Note: Do Not Use HTTP Server In Production

Live Reload

Genix continuously monitors your working directories for changes. When updates are detected, it automatically regenerates the necessary static files. This provides immediate feedback, allowing you to iterate quickly without the need for manual rebuilds or refreshes.

Error Logging

Genix includes a built-in error logging system to help identify and resolve issues during development. Parsing errors will indicate the file, line number, and character position where the issue occurred. Logs are categorized into the following levels:

  • Information — General status updates on the build process.
  • Warnings — Non-critical issues that may still need attention.
  • Errors — Problems that prevent successful generation of specific files.
  • Fatal — Critical issues that halt the build process.

An additional Debug channel is also available, but only when the debug flag is enabled. This provides extra detail useful for troubleshooting complex issues.

Customizing Log Levels

You can configure which types of logs are written to the log file by adjusting the active log level. This allows you to focus on the level of detail most relevant to your current workflow, whether that’s general information or deep debugging output.

Scroll To Top