|
|
See the table of contents `---------------->`
|
|
|
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.
|
|
|
|
|
|
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. The current website at https://civicrm.org is a mix of various efforts over the past several years, resulting in what most feel largely misses the mark.
|
|
|
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.
|
|
|
|
|
|
One of the central operation objectives of the CiviCRM Core Team has been ecosystem growth. The website is likely the project's single largest asset with respect to overall growth.
|
|
|
This intiative can be broken down into 3 distinct areas of work:
|
|
|
|
|
|
# Objectives
|
|
|
1. Technical review - which CMS, what extensions, what additional custom code is necessary, costs to transition, costs for ongoing maintentance, etc.
|
|
|
2. Content production and site structure - identify, revise, draft proper content and organize it in a way that is consistent with the site's audience and objectives.
|
|
|
3. Branding and design - identify and communicate our key messages (unique selling points), our overall "brand" and what CiviCRM stands for, and leverage design to reinforce these.
|
|
|
|
|
|
- The site should be multi-lingual from day one. 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.
|
|
|
# Functional Objectives
|
|
|
|
|
|
The following are identified as primary objectives of the ideal website for CiviCRM:
|
|
|
|
|
|
- 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](https://lab.civicrm.org/marketing/social-media) efforts, become more responsive.
|
|
|
- The site should as little custom code as possible. When code is necessary, we should endeavor to create generic extensions.
|
|
|
- The site should use as little custom code as possible. When code is necessary, we should endeavor to create generic extensions.
|
|
|
|
|
|
# Project Details
|
|
|
|
... | ... | |