Hi there, I’m currently building a sort of web app using Kirby as a backend and I have a small dilemma. I’ve been wondering, where should I be saving common/site wide/global information that should be customizable? From what I can gather, there’s 2 places where you usually save global info. site.t…

This is what I’ve been doing: User visible information or setting that needs to be maintained be a non-technical person are stored at site.txt: title, description, social links and so on… API keys, Google Analytics code, email settings are stored in environment variables then used in config files

[image] pedroborges: maintained be a non-technical I think this is the criteria the makes the most sense to me. Thanks! I also assume that sensitive information shouldn’t be found in site.txt since the content is readable by the browser.

Where to save global/site wide information?

The CMS Questions

texnixe February 16, 2016, 4:30pm 3

I’d say anything that needs to be accessible/editable by panel users, should go into site.txt, the rest into config.php.

Good practice for theme settings?

Topic		Replies	Views
Site Wide Information Questions v3	2	268	January 31, 2020
Setting a site-wide variable Questions v2	7	1052	November 28, 2016
Set config vars c::set (); in a page Questions v2	8	1877	April 2, 2015
Best Practices for global settings in Kirby Questions	2	113	February 3, 2025
Modify Config in a multi config environment - best practices Questions v5	5	83	February 1, 2026

Where to save global/site wide information?

Related topics