> If I understand correctly, you should run the script that serves the config file to i3 each time a modification is done, like restarting httpd every time you modify a config file, am I right?
Actually I haven't thought through the best update strategy yet. At this time, the generated i3 file is produced when the desktop session is loaded. In Regolith there is a script that handles refreshing the desktop session from source files (Xresources, and now config partials). It will at least be added to that, so via either a command or keybinding the user can manually refresh their desktop. Automatic refresh sounds interesting but would have to think through all of the edge cases. As Regolith relies heavily on the package manager for configuration, perhaps each partial (represented as a package) would cause the session to be refreshed via postinst and postrm scripts.