[Docs] Add related article

spatie · Jan 10, 2025 · d4b9db4 · d4b9db4
1 parent 545e509
commit d4b9db4
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/docs/best-practices/roles-vs-permissions.md b/docs/best-practices/roles-vs-permissions.md
@@ -32,3 +32,6 @@ Summary:
 Sometimes certain groups of `route` rules may make best sense to group them around a `role`, but still, whenever possible, there is less overhead used if you can check against a specific `permission` instead.
 
 
+### FURTHER READING:
+
+[@joelclermont](https://github.com/joelclermont) at [masteringlaravel.io](https://masteringlaravel.io/daily) offers similar guidance in his post about [Treating Feature Access As Data, Not Code](https://masteringlaravel.io/daily/2025-01-09-treat-feature-access-as-data-not-code)