diff --git a/README.md b/README.md
index b3c9966..6916e39 100644
--- a/README.md
+++ b/README.md
@@ -65,26 +65,26 @@ Otherwise, go ahead and add these to your `application.properties` file:
```properties
## The first-level part of the URL path: http://localhost:8080/${baseUrl}/
-dbadmin.baseUrl=admin
+snapadmin.baseUrl=admin
## The package(s) that contain your @Entity classes
## accepts multiple comma separated values
-dbadmin.modelsPackage=your.models.package,your.second.models.package
+snapadmin.modelsPackage=your.models.package,your.second.models.package
## At the moment, it's required to have open-in-view set to true.
# spring.jpa.open-in-view=true
## OPTIONAL PARAMETERS
## Whether to enable SnapAdmin
-# dbadmin.enabled=true
+# snapadmin.enabled=true
#
#
## Set to true if you need to run the tests, as it will customize
## the database configuration for the internal DataSource
-# dbadmin.testMode=false
+# snapadmin.testMode=false
#
## SQL console enable/disable (true by default)
-# dbadmin.sqlConsoleEnabled=false
+# snapadmin.sqlConsoleEnabled=false
```
**IMPORTANT**: The configuration prefix `dbadmin.` will change to `snapadmin.` starting from version 0.2.0, as part of the project being renamed. Remember to update your configuration files accordingly.
@@ -97,7 +97,7 @@ Now annotate your `@SpringBootApplication` class containing the `main` method wi
This will autoconfigure SnapAdmin when your application starts. You are good to go!
-3. At this point, when you run your application, you should be able to visit `http://localhost:${port}/${dbadmin.baseUrl}` and see the web interface.
+3. At this point, when you run your application, you should be able to visit `http://localhost:${port}/${snapadmin.baseUrl}` and see the web interface.
## Documentation
diff --git a/docs/css/style.css b/docs/css/style.css
index 5630077..3ea5770 100644
--- a/docs/css/style.css
+++ b/docs/css/style.css
@@ -41,3 +41,13 @@ p.text {
a {
color: #7223D1;
}
+
+
+.testimonials-img {
+ width: 33%;
+}
+
+.testimonials-img img {
+ border-radius: 50%;
+ border: 1px solid #CCC;
+}
\ No newline at end of file
diff --git a/docs/docs/index.html b/docs/docs/index.html
index 696c4bf..d846192 100644
--- a/docs/docs/index.html
+++ b/docs/docs/index.html
@@ -96,25 +96,25 @@
## The first-level part of the URL path: http://localhost:8080/${baseUrl}/
-dbadmin.baseUrl=admin
+snapadmin.baseUrl=admin
## The package(s) that contain your @Entity classes
## accepts multiple comma separated values
-dbadmin.modelsPackage=your.models.package,your.second.models.package
+snapadmin.modelsPackage=your.models.package,your.second.models.package
## At the moment, it's required to have open-in-view set to true.
# spring.jpa.open-in-view=true
## OPTIONAL PARAMETERS
## Whether to enable SnapAdmin
-# dbadmin.enabled=true
+# snapadmin.enabled=true
#
## Set to true if you need to run the tests, as it will customize
## the database configuration for the internal DataSource
-# dbadmin.testMode=false
+# snapadmin.testMode=false
#
## SQL console enable/disable (true by default)
-# dbadmin.sqlConsoleEnabled=false
+# snapadmin.sqlConsoleEnabled=false
@@ -344,11 +344,11 @@ public class Payment { ... }
3.2 The Settings panel
-As mentioned earlier, the Settings panel primarily provides options to customize the branding/appearance of the web interface. These settings are persistent across restarts and are stored in an embedded H2 database (file named dbadmin_internal), along with other data required by SnapAdmin.
+As mentioned earlier, the Settings panel primarily provides options to customize the branding/appearance of the web interface. These settings are persistent across restarts and are stored in an embedded H2 database (file named snapadmin_internal), along with other data required by SnapAdmin.
4. Security
SnapAdmin does not implement authentication and/or authorization mechanisms. However, you can use a standard Spring security configuration in order to limit access to the web UI or specific parts of it.
-All SnapAdmin routes start with the value of dbadmin.baseUrl property, and all write operations (edit, create, delete) are implemented as POST calls. The following code provides an example security configuration (assuming SnapAdmin runs at /admin):
+All SnapAdmin routes start with the value of snapadmin.baseUrl property, and all write operations (edit, create, delete) are implemented as POST calls. The following code provides an example security configuration (assuming SnapAdmin runs at /admin):
diff --git a/docs/index.html b/docs/index.html
index 9f7da2d..3d28cf3 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -58,7 +58,7 @@
Features
-
SnapAdmin scans your existing code base and automatically builds everything at runtime: you won't have to modify your existing code.
+
SnapAdmin saves you time by providing a full-fledged database management interface so you can focus on what matters. It won't be necessary to modify your codebase: SnapAdmin scans your code and builds everything at runtime.
First-class CRUD
@@ -110,10 +110,10 @@
Add the minimum required properties to your application.properties file.
# the root path of all SnapAdmin routes
-dbadmin.baseUrl=admin
+snapadmin.baseUrl=admin
# comma-separated list of packages to scan for @Entity classes
-dbadmin.modelsPackage=your.models.package
+snapadmin.modelsPackage=your.models.package
@@ -132,26 +132,48 @@ dbadmin.modelsPackage=your.models.package
+
+
+
+
Who is using SnapAdmin
+
Here's what some of our users say about SnapAdmin. You can leave your comment, too!
+
+
+
+
+
+
+
fabienfleureau
+
Hello,
+ Thanks for you project.
+ I use it an hidden admin page, mostly as if it is a direct connection to database.
+ It would be nice to able to run custom queries.
+
+
+
+
+