valan Posted July 31, 2014 Share Posted July 31, 2014 I've married PW about 2 years ago and I feel happy today. However, this fact also gives me some rights to share thoughts how to direct PW development with the objective to speedup popularity and better fuel its development. List below - something that is on top of my mind. Sorry if I'd repeat already discussed topics. The purpose is to summarize really top "big" things in one place and give core team source for thoughts.1. Any more or less popular/really important site needs a development "copy" and usually test "copy", were developers/testers can do whatever they want, passing changes through dev->test->production approval chain. These features should attract more web-developer teams and those who do something bigger than personal blog-site. ) Ideally this should be integrated with git/bit-buckets to make version management easy.2. Any more or less "commercial" site needs well-developed "payment plugin". Existing PW plugin(s) are far from desired state. I'd suggest to make it and place it in core. This should attract more "commercial" web-developers into PW and those who consider PW as next CMS but don't have good PHP background. BTW, I'd suggest to consider https://github.com/omnipay/omnipay as a basis for such "to-be" PW plugin.3. Most popular front-end framework is bootstrap. Why not to "bootstrap3" PW admin? It will close the gap btw frontend UI and admin UI (forms, inputs, etc) for majority of web-developers. E.g. no need to design own forms/inputs and to some extent server logic, etc. There is great Ryan's Formbuilder module, but I talk here about design & custom forms for non-generic use cases. Also, number and design of input fields should be reviewed to close at list 80% of web-developer needs. I'd also welcome "save-as-type" mode of entry vs current "type-find save button-waitrefresh".4. PW community has grown and forum has become a hard place to find answers quickly, especially for new PW-engaged people. Actually what any web-developer needs is manual (like PHP manual) and stackoverflow q&a system. May be it is time to open PW stackoverflow, while maintaining manual? Additions/corrections/critics - welcome! Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now