... | ... | @@ -9,15 +9,17 @@ The following are identified as primary objectives of the ideal website for Civi |
|
|
- The site should be multi-lingual. Many non-English speaking countries represent growth markets for CiviCRM. In its current form, CiviCRM is very competitive in its internationalization. Many non-English speaking countries have favorable views of open source.
|
|
|
- The site should clearly explain what CiviCRM is and how it can be used. It should provide easy access to decision makers that come to the site to learn about what CiviCRM is and what it can do.
|
|
|
- The site should clearly funnel more community focused users and developers to resources they need to become more productive faster, and to get and stay engaged with less effort. The site must make it dead simple to get involved with CiviCRM.
|
|
|
- The site should be exceptionally easy to manage and adjust. CiviCRM is often slow to respond to market opportunities and should, in conjunction with its social media efforts, become more responsive.
|
|
|
- The site should be exceptionally easy to manage, maintain and adjust. CiviCRM is often slow to respond to market opportunities and should, in conjunction with its social media efforts, become more responsive.
|
|
|
- The site should use as little custom code as possible. When code is necessary, we should endeavor to create generic extensions.
|
|
|
- The site should seek to more clearly position CiviCRM Spark as a viable option for onboarding new users and CiviCRM ESR as a viable option for slower adopters.
|
|
|
- This effort should endeavor to use as much volunteer support as possible.
|
|
|
|
|
|
This intiative can be broken down into 3 distinct areas of work:
|
|
|
|
|
|
## 1. Technicalogy & infrastructure
|
|
|
|
|
|
Which CMS, what extensions, what additional custom code is necessary, costs to transition, costs for ongoing maintentance, etc.
|
|
|
- The 2 primary candidates to which civicrm.org may transition are Drupal 8 and WordPress. [Comparing Drupal 8 vs. WordPress](https://lab.civicrm.org/marketing/civicrm-website/wikis/2019-cms-upgrade)
|
|
|
- The 2 primary candidates to which civicrm.org may transition are Drupal 8 and WordPress. [Comparing Drupal 8 vs. WordPress](https://lab.civicrm.org/marketing/civicrm-website/wikis/WordPress-vs.-Drupal-8-Comparison)
|
|
|
- Initial testing has been completed on an [upgrade to Drupal 8](https://lab.civicrm.org/marketing/civicrm-website/wikis/drupal8-upgrade-test) with [ongoing discussion captured here.](https://lab.civicrm.org/marketing/civicrm-website/issues/130)
|
|
|
- [This page documents current functionalities](https://lab.civicrm.org/marketing/civicrm-website/wikis/Current-Site-Core-Functions), however these could change and may not necessarily need to be redone/duplicated to a new site. Examples of proposed changes that reduce CMS dependencies can be found [here](https://lab.civicrm.org/marketing/civicrm-website/issues/139) and [here](https://lab.civicrm.org/marketing/civicrm-website/issues/138).
|
|
|
|
... | ... | |