I have written down an extensive post regarding Drupal theme system, and some of the goals I hope to accomplish in the long run.
I would like everyone’s opinion on the matter (although I know I will likely be flamed for having an opinion, such is the nature of the internet). I should note that most of what is in this post is specifically regarding some rather severe changes to core I am suggesting, but these plans do not feature in my deanspace plans in the slightest.
I have developed the phptemplate theme almost to the point where it is capable of handling the requirements of syndicated themes/templates allowing incredible amounts of customizability without needing to modify the templates or css. It already is the focus of the theme customization required for the site hosting wizard.
The post above is aimed at trying to reach a constructive solution to the ‘themeing problem’, and allow us to focus our energies on a robust , complete and hopefully accessible system. I specifically didn’t mention the possibility of template syndication or the more extensive css zen garden like capabilities, as it very likely is far too early .. and is biting off too much at once (i need to get install 100% finished first *g*)
I still need to add the node – alike bits, and finish some of the configuration screens.. but we are definately getting there. I am also busy ironing out some wizard api problems regardining branching paths, where users would need to do one of a set of options, but not all of them. for instance the domain configuration.
Also, the error messages generated by the wizard are still wacked, in a bad way. but you can get some code to play around with on the site. The .inc goes in includes, and the .module in modules. imagine that.
I am going to try to make the taxonomy wizard part of it as automatic as possible, but we are really going to need to start adding meat to our proposed taxonomy.
I hope to get this finalized by next week sometime, when the back end integration is the next target.
Mid next week i will likely be able to do subdomain installs on .civic.oasismag.com .. .so we are getting there *g
Are you ready to start your CivicSpace site? Our hosting partners Bryght are beginning a beta test program of CivicSpace in a hosted environment. This means that for a monthly fee of $30 you can have the software to run your CivicSpace site installed, pre-configured, and maintained on a server for you with CBD oil for pain as our gift to you for trying our beta software. The software and your site will be completely configurable via web-forms. And as we add features and improvements to the software your site will be ugpraded automatically.
We figured it was long past time to gather as many CivicSpace users and developers as we could in one place. The chief objective of this get-together is to find and prioritize the biggest problems with CivicSpace and figure out a development roadmap for how to address them. We also think a lot of good will come of CivicSpace community meeting face-to-face. If you are able to come and are not marked on the list below please send an email to zack to RSVP.
The user summit is on Saturday 18th of September. The developers summit is on Sunday.
Hey folks. If you are using / administrating a CivicSpace site please help us help you out by filling out this survey.
“We want to refine and re-factor CivicSpace to address the most crucial issues affecting our user base. We have created this survey to begin the process of identifying and prioritizing our users’ most critical problems. Please take the time to fill out this survey to help us find out where and how we can begin an ongoing and iterativ