I come from a .Net background and Simple CRM is a SPA website I built in order to teach myself JavaScript, Meteor, React, Redux, Git etc. I've been working on it fairly full time for around 6 weeks, but beware that I only started learning JavaScript about three months ago.
I hope that, after I incorporate feedback from more experienced developers, Simple CRM can become a valuable resource to the community that provides the next step in learning after the Todo app examples. That was a resource that I was desperately looking for but never found when I was learning.
Sorry to say the online demo has now gone as Meteor.com free hosting is no longer available and I haven't had time to investigate alternate free hosting.
The code tries to provide examples of all of the common stuff you need to write for line of business and data-centric apps.
Namely:
- Data entry forms
- Business logic
- Validation logic
- Real-time validation
- CRUD
- Relationships and relational integrity
- Data denormalization
- Async auto-complete
In time it will also include
- Security
- Charts
- Paper reporting
- Excel export
- Testing
If you haven't seen Meteor 1.3's recommended application structure yet you may be wondering where the actual code is.
The UI Is here https://github.com/tomRedox/simpleCRM/tree/master/imports/ui and the API is here https://github.com/tomRedox/simpleCRM/tree/master/imports/api
This version of Simple CRM uses the following stack/technologies:
- Meteor 1.3
- MongoDB
- React for the view layer
- Redux for the application state
The instructions below assume you've already installed Meteor on your machine.
- Clone this repository to your machine:
git clone https://github.com/tomRedox/simpleCRM.git - Change to the project's directory:
cd simpleCRM - Install the version of Meteor used by this project:
meteor update --release 1.3-beta.12(you can have multiple versions of Meteor installed on a machine, so this shouldn't upset any other projects. Meteor stores which version to user for a particular project in the .meteor/release file) - Install the npm modules used by the project:
npm install
Then run the project with meteor. The login credentials are: email: [email protected] password: default@admin.
The app is running on Meteor 1.3 Beta 12 and will not work with Meteor 1.2.
I've tried to adopt the standards laid down in the Meteor guide, especially:
- Application structure that uses main.js entry points and puts the rest of the code in imports directories (ES2015)
- Container pattern
- Template level data subscriptions
- Use of MDG validated methods
- No AutoPublish or Insecure
The view layer is built in React, with each component in its own file. I've tried to follow React best practice, although defining exactly what constitutes best practice at present is difficult as React and Redux are still changing so often.
I've used Redux for managing the application state. However, I do not put the stored data in the state, I leave MiniMongo out of Redux altogether. I do copy data into the state while it's being edited however, I do this to make the record being edited non-reactive during the edit (I don't want the data the user sees to change while they are editing it) and in order to allow real-time data validation.
There is also a "no-redux" branch that features the older working version of the system before I switched over to Redux. That may be interesting to those wishing to see what an app looks like with and without Redux. I won't be maintaining the no-redux branch, it's just for info.
At the moment I've done the basics to get things up and running, but little in the way of design work has gone into the project so far.
The design consists of:
- Material design-esque theme from Bootswatch
- Parts of the SB Admin 2 Bootstrap theme
I have also experimented with the excellent Material-UI React component library and I may adopt that at some point. There is a separate branch for that work
The app now has security based on Meteor's in-built security API. The login credentials are: email: [email protected] password: default@admin
There are a couple of unit tests for the business logic in the lib folder. The testing has been built using the instructions in the draft Testing chapter of the Meteor Guide.
To run the tests open up a second command window and type:
meteor test --driver-package avital:mocha --port 3100
This starts the test runner which will automatically rerun the tests as required.
You can then view the test results at http://localhost:3100/.
I need to feed the changes from our production dev back into this project, namely:
- ES6 syntax
- Functional stateless components
- Meteor 1.3 final
- Updates to the testing frameworks
Other broad areas still to be looked at in the project are:
- IsDirty checking to warn before navigation when changes have been made
- Unit tests
- End-to-end/integration test
- Add Airbnb's linting
- Security - only return and write data for logged in users
- Security - add Admin role, only Admin to be able edit the Products list
- Charts
- Paper reporting
- Excel export
- Improve/fix the transition animations
- Customer deletion
- Customer search page - allow search on address, name and postcode
- Pagination on All Customers and All Orders pages
- Sorting options on lists
I am hugely grateful to the Meteor community and the members of the SpaceDojo/Meteor Club Slack channel for all their help getting up to speed on everything.
These are some of the many resources that have really helped me:
- Meteor Guide
- Meteor Guide 1.3 (draft)
- Meteor Forums
- Rob Conery's Building a Realtime Web Application with Meteor.js Pluralsight course
- SpaceDojo and the SpaceDojo community
- Meteor Chef
- Meteor Chef - Click to edit fields in react
- Stack Overflow
- Cory House's Building Applications with React and Flux Pluralsight course
- Official React documentation
- Official Redux documentation
- The official guidance from the draft Meteor Guide for Meteor 1.3
- The official React example app, main React branch
- The official React example app, React with Tests branch
- Discussion of the Container pattern and how to stop React components rendering before the data is available
If you don't know Redux yet, then learn:
Start with this series:
- Abhi Aiyer's How we Redux series - Part 1
- Abhi Aiyer's How we Redux series - Part 2
- Abhi Aiyer's How we Redux series - Part 3
- Abhi Aiyer's How we Redux series - Part 4
- Abhi Aiyer's How we Redux series - Part 5
- How we Redux example app repo
But also open up this example and have it to refer to too:
And also this is really useful:
- AdamBrodzinski's meteor-flux-helpers
- Discussion of meteor-flux-helpers
- Redux version of meteor-flux-helpers example app
Other useful bits:
We write bespoke line of business software for small and medium size businesses.
Read all about us at http://www.redox-software.co.uk/.