-
Notifications
You must be signed in to change notification settings - Fork 22
Site-wide data models #19
Comments
I just realised that putting the legal footer text into a setting will complicate translations. If this text is not likely to change often then the simplest approach in my view is to hard-code it into the template, so that it can be translated in the normal way. The same potentially applies for the navigation/footer menu items as well. I notice that on the current site, the top navigation is only available when viewing the site in English. |
The top nav is only in English because the Foundation site itself is mainly only in English. |
I've been looking into how to store currency information, and feel that we're best off having a hard-coded dictionary very similar to the current one. The rationale for this is that this data doesn't change frequently, and so it doesn't seem worth the cost of modeling in the database and making editable in Wagtail. @alanmoo @TheoChevalier does this sound OK to you? |
@solarissmoke No issue on my side, thanks for asking :) |
Closing on the basis that we've ended up storing all of this information in code, so no site-wide models necessary at present. |
Out of curiosity (because we might need it on our other Wagtail site) is there any documentation on best practices for site-wide model implementation? |
Yes - use |
I propose to use site-wide settings to store the following:
It might be easier to store currency information in code instead - to make a call before starting work on this.
The text was updated successfully, but these errors were encountered: