Whether you're just getting started with customizing CiviCRM or you already think you know everything about it, I invite you to spend a few minutes playing with the new API Explorer in 4.6. You'll be glad you did.
Having gone on long car journeys with young children before the ACPED (Age of Cheap Personal Electronic Devices), I am very familiar with “Are we there yet?” Now I usually only hear it in my head as I try to make light of the longer than 12-hour flights I have to endure as an Australian who likes to attend CiviCon. Lately, however, it is there whenever I visit the CiviCRM Area 51 site on Stack Exchange. I want to be at the “beta” phase when we will actually be able to ask and answer questions.
As you may have heard, CiviCRM is about to launch an exciting new help site on Stack Exchange, which will make getting support with CiviCRM easier and more effective.
The new site is about to launch, but the initial "beta" phase will only be available to a limited group of people. This pilot group will have unprecidented access to world's top CiviCRM experts, and it's not too late for you to join them.
As you may know from a recent blog post by artfulrobot, CiviCRM is applying for a dedicated platform on Stack Exchange. I don't know about you, but I would love to see this happen. (If you wonder what this is all about, please refer to the beforementioned blog post which explains it very well.)
This initiative needs backing from Stack Exchange veterans now! Here is why:
After the excitement of CiviCon with new features and extensions being discussed, the Civi Sprinters are hard at work improving and finalising these for release, as well as discussing future plans.
However not all of us can bask in the glory of cool features and improvements. The documentation team have been hard at work attempting to improve the Civi Book.
Good testing is critical for providing quality software. Some testing is always manual but writing automated tests to do the heavy lifting is a key part of modern coding practices. For developers, the discipline of writing automated tests helps to proactively identify and control edge-cases, and regularly running tests helps to identify problems quickly (before they grow and cause greater harm). Fostering a healthy culture of testing requires easy, consistent, timely test-results which in turn requires an easy, consistent, quick way to setup a new test environment.
"...not on those days."
"...I am very new to CiviCRM."
"...I don't understand what I need to do."
Read more for answers to you concerns.