Welcome to my fourh episode of my LaSalle Software News podcast.
This is Bob Bloom, from Toronto Canada.
Today is Friday, February 12th, 2016.
I publish LaSalle Software News monthly, at the top of the month, to update you on my LaSalle Software.
Except for this month, when I purposely waited to tag version 1.01, my first client-ready release.
Instead of telling you what was going to happen, I preferred to announce its release.
I am thrilled to announce the release of LaSalle Software Version 1.01. This release is the first version of my Software that I am confident in installing for clients.
It is the first major release after tagging version 1.0 in November. Since that release, I have live deployed six of my own LaSalle Software web applications on Digital Ocean servers, using the Laravel "Forge" service. My web apps have performed well and are stable. I have smoothed out many rough edges, and have added more features such as Two Factor Authorization.
LaSalle Software was originally intended to be scaffolding software, to give my clients a head start when building their custom web apps. It is not scaffolding, it is a full fledged content system with user management, login/logout/registration handling, 2FA, a full admin back-end, and admin form automation to speed up custom development. There are optional apps, such as a to-do app, and a customer database app, that can be installed.
LaSalle Software is comprised of composer installable packages. Some packages are mandatory, and some are optional.
LaSalle Software uses PSR-4, abides by PSR-2 coding standards (mostly), uses composer for package installation, and integrates a number of fine third party packages for the site map, image handling, and backups.
Emphatically, there are no proprietary modules, nor proprietary templating schemes. The point is to stick with the growing composer-installable package libraries; and, with the Laravel eco-systems.
LaSalle Software includes a content system, which includes micro-tags, meta-tags (still need the meta-descripton for search results), unlimited tags, the option to create static pages, built-in image handling, future dated publishing, and a bunch of other stuff I can't remember.
What you have to do is build a front-end, because I do not have pre-built templates. Which I do on purpose, because low to mid budget sites under-invest in their front-ends. At least in my opinion.
I wanted to create web application software that got my clients over the last hump. Web app server and deployment costs have come down like a rock; and, that techology has improved by leaps and bounds over the last few years. The Laravel Framework is a superb, modern, web application framework with which to base our web apps.
What was missing was the basic software that everyone needs as the basis for their own custom web applications. I want to provide that software to you, the software that has the basic content management, the basic user management, the basic login authentication -- essentially, the necessary software scaffolding.
The scaffolding that I wanted did not exist. So I built my own. Which became a lot more than simple scaffolding. The features are more fully built-out than what basic scaffolding provides. My clients have quite a head start now with their custom web app development.
Now, web app development is accessible to those who would otherwise use WordPress or similar.
LaSalle Software is not feature complete.
There is a glaring inability to search the server for existing images to use. I assumed that such a package exists, but I have not found this package; nor, have I built this package.
There are no access control levels beyond that you have to be a "Super Administrator" to log into the back-end. The scope of ACL development has increased so much that I have left its development for after v1.01's release.
LaSalle Software is designed to bring out the value of custom web app development. It provides a solid footing for further custom development, saving my clients five (or six?!) figures not having to conjure up the base feature set that everyone needs for their web apps themselves.
I am thrilled to announce that I am building a volunteer proof-of-concept web application for my synagogue. It will be a live test-bed for software I was going to develop anyways, but now that there is a real web app the quality of the software will increase.
Later this month, I will start LaSalleMart API development. This ecommerce API will be a real API, not just an internal API.
I will use RAML and MuleSoft tools to build my API.
I have a series of articles about this major LaSalle Software release. For further info, dive in!
You have been listening to a SouthLaSalleMEDIA.com production. Opinions expressed are not necessarily those of SouthLaSalleMEDIA dot com, nor of the organizations represented. Links and materials discussed on air are available in the Show Notes for this show. Information contained herein have been obtained from sources believed to be reliable, but are not guaranteed. Podcasts are released under a creative commons licence. Some rights are reserved. Email correspondence to the attention of Bob Bloom at info at SouthLaSalleMedia dot com.