Why AutoBackOffice is the best solution
When you need to develop a medium/small website, there are mainly two ways: either you go the "Wordpress" way, or you write a website from scratch.Both have pros and cons, but the main problem with a custom website is that you need to build ALSO a backoffice, to give your customer the chance to modify the database.
There are some products on the market, both free and paid, but we could not find the perfect solution, so we wrote our own, and ABO AutoBackOffice was born.
You see, the free ones are - frankly - ugly looking, and they are really made by engineers for engineers. A typical end user has a lot of problems understanding 90s-style icons, cryptic DB-like names, and so on, and so you cannot really use those.
On the other hand, some of the paid-for ones became so complicated to install, use and configure that, nowadays, not only it takes a lot of time to make them working, but as soon as you modify your website, it takes literally HOURS to update them too.
How is ABO AutoBackOffice different?
First of all, it's based on Bootstrap, so it's fully responsive and the graphical interface is on par with the latest trends - and this helps the final user.
But most of all, it literally takes MINUTES to configure even the most complicated project, and if - for example - you add a field to the database, the only thing you need to do is to press "Rescan DB" on ABO, that's it! No re-compiling, no re-upload, no re-testing... And this is what we wanted to achieve: to let you focus on the website itself, and to let the backoffice be just a small part of your job, almost self-generating.
And talking about self-generating, we added some useful features like the automatic documentation generation, so that you can deliver a professional-looking documentation to your customer at no cost! We all know that there is usually no time to write documentation, not even a basic one, but with ABO you can give your customer not one, but TWO different documentation: one about the data that they can enter, and the second the technical details of your DB, in case somebody is interested and/or can better understand how to use your website.
