|
|
CiviCRM will begin a transition off of D7 in the coming months and is evaluating this effort to also coincide with a major site revision.
|
|
|
|
|
|
A central operational objective of the CiviCRM Core Team has been ecosystem growth. The website is the project's single largest asset with respect to overall growth, so this 'transition' needs to account for both the technical aspects as well as the non-technical.
|
|
|
The CiviCRM community recognizes that ecosystem growth is key to its sustainability and to the overall health of the project. The CiviCRM website is the project's single largest asset with respect to overall growth, so this 'transition' needs to account for both the technical aspects as well as the non-technical.
|
|
|
|
|
|
# Functional Objectives
|
|
|
|
... | ... | @@ -16,7 +16,7 @@ The following are identified as primary objectives of the ideal website for Civi |
|
|
|
|
|
This intiative can be broken down into 3 distinct areas of work (below) with examples of how [other projects achieve these found here](https://lab.civicrm.org/marketing/civicrm-website/wikis/Peer-Sites):
|
|
|
|
|
|
## 1. Technicalogy & infrastructure
|
|
|
## 1. Technology & 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/WordPress-vs.-Drupal-8-Comparison)
|
... | ... | |