From b82607a31cc35cc0236466a5ed6f8686153be30b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gabor=20K=C3=B6rber?= Date: Wed, 6 May 2026 19:32:29 +0200 Subject: [PATCH] . --- rear_auth/roadmap.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/rear_auth/roadmap.md b/rear_auth/roadmap.md index 89c4159..1f7bd8d 100644 --- a/rear_auth/roadmap.md +++ b/rear_auth/roadmap.md @@ -1,2 +1,6 @@ Atm. it is not clear to me if rear_auth will really be it's own package, as it needs to interact a lot with rear, or if I split up rear into modules instead. +Another idea would be to: + - create rear as a basic set of tools for a homepage, like commonalities you would require + - transform rear_auth into rear_admin, utilizing the repository patterns and template engines from rear for providing an admin interface + \ No newline at end of file