ambiser
/
strapi-plugin-config-sync
mirror of https://github.com/boazpoolman/strapi-plugin-config-sync
9
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #184 from mccrackend/patch-1 

Documentation typo, fixing broken link
pull/185/head
Boaz Poolman 2025-05-29 17:19:56 +02:00 committed by GitHub
parent c6e865bec1 a2a136a336
commit 8becc53ddf
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/getting-started/admin-gui.md
View File

@ -10,4 +10,4 @@ This plugin ships with a React app which can be accessed from the settings page
**Pro tip:**
By clicking on one of the items in the diff table you can see the exact difference between sync dir and database in a git-style diff viewer.
<img src="/img/assets/admin-diff-viewer.png" alt="Config diff in admin" />
![Config diff in admin](/img/assets/admin-diff-viewer.png)

2
docs/docs/getting-started/motivation.md
View File

@ -6,7 +6,7 @@ slug: /motivation
# 💡 Motivation
In Strapi we come across what I would call config types. These are models of which the records are stored in our database, just like content types. Though the big difference here is that your code ofter relies on the database records of these types.
In Strapi we come across what I would call config types. These are models of which the records are stored in our database, just like content types. Though the big difference here is that your code often relies on the database records of these types.
Having said that, it makes sense that these records can be exported, added to git, and be migrated across environments. This way we can make sure we have all the data our code relies on, on each environment.