Ci3 Starter Project
This project is based on the CI_bootstrap_3 and my vison for an efficient system and simple.
Using CodeIgniter 3
- Front-end
- Bootstrap 3 (and themes)
- Google Fonts
- Back-end
- AmdinLE
- Auth system (ability for front-end users and back-end users)
- Multilang (maybe read the translation CI3 files and display them editable on the backend)
- less compiler
minify css ans js (maybe...)
-
utilities to build on the backend
- Grocery CRUD (v1.5.1) - feature-rich library to build CRUD tables
- Image CRUD (v0.6) - CRUD library for image management - Creating a media library
- File navigator and editor
- Wysiwyg text areas, based on AdminLE proposed solution (CFKEditor)
- Databse table editor
user management - create/edite/delete Users and Roles
Form builder, maybe look at the ideas on Bolt files for content types and forms.
- less variables graphical editor... scan less files, find variables, and put them on the backoffice in a list with a color picker and space to fill css properties.link
Important side goals:
- Deployment is copy/paste
- Urls are relative, avoid the Wordpress mess on moving sites around
- Database is sqllite (using htaccess to protect web access to DB),
- can be Mysql, but the copy/paste deplyment gets a bit more complicated
- Possibility to have development environment and production environment on the same place (staging)
- Smart embedd - Like paste url on facebook or wordpress and automatic embedd of video or page thumbnails... think better about this.
Simple setup configuration - Have a single file to configure the app, not a single folder with many files like CodeIgniter has.
-
Desirable - Could be important to have newsletter capabilities...
- mode simple:
- Works from the system
- have a hand-mantained template.
- send mails from CI3 directly,
- manage mailing list
- subscribe "shortcode" (like wordpress shortcodes)
- seems a lot of work and difficult to have quality solution
- mode integrated:
- setup api key and integrate with some mailing system (mailchimp, mailgun, ...)
- use the foreign system api to provide an embedded solution, ie., managing the lists, and creation and sending of emails is done on backoffice and we use API to call 3rf party services.
- seems a lot of work, makes the system dependent on 3rd party
- mode outOfTheWay:
- provide a skeleton subscribe form for capturing email addresses and store them.
- provide an export list to a format easy to import on those 3rd party systems (csv) and use them separate from our app.
- ** probably try this**
- mode simple:
Current differences with original:
- I want simple, so no GLUP, no commandline tools required (but it should be possible to call composer one day)
- no migrations. At the moment, migrations seem like an overhead, we only want to go forward not go back.