Re: Introducing JobBoardr
I’ve actually been thinking about what to do with the CV part of the component. I’ve basically got 3 choices right now.
1. Leave it as it is right now. CVs are part of the main component and can be deactivated, but do not work as a stand-alone plugin. Not a big fan of this.
2. Make the CV bits a stand-alone plugin. If JobBoardr is present, then integrate it. Downside of that option is, that you’d have to purchase 2 plugins instead of just 1 if you want the job bits as well.
3. Build a cheapish web service with an API that integrates with JobBoardr.
I quite like option 2 for better flexibility. Option 3 will only be viable if the CV component grows too big (which it might do…). To be honest, option 1 probably won’t last…
What do you think?
