... | ... | @@ -10,10 +10,10 @@ One of the central operation objectives of the CiviCRM Core Team has been ecosys |
|
|
- 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.
|
|
|
|
|
|
# Tentative Project Plan
|
|
|
# Project Details
|
|
|
|
|
|
- [Clean up current website](https://lab.civicrm.org/marketing/civicrm-website/issues/127)
|
|
|
- Stage/test D8 upgrade
|
|
|
- Pull the trigger on D8 or WP
|
|
|
- Implement multilingual |
|
|
\ No newline at end of file |
|
|
- [Issues and tasks](https://lab.civicrm.org/groups/marketing/-/issues?milestone_title=CiviCRM+Website+Upgrade)
|
|
|
- [Overview of current site structure](https://lab.civicrm.org/marketing/civicrm-website/wikis/site-structure)
|
|
|
- [CMS upgrade testing](https://lab.civicrm.org/marketing/civicrm-website/wikis/2019-cms-upgrade) |
|
|
\ No newline at end of file |