|
|
[[_TOC_]]
|
|
|
|
|
|
# Scope
|
|
|
|
|
|
We don't know yet which will be the next CMS (see #141 and #130), but we know that no matter what the solution, some pages/features will need to be worked on. This page tracks this at a high level.
|
|
|
|
|
|
# Design philosophy
|
|
|
|
|
|
* Keep using a Bootstrap-based solution (v3 or v4) - because everyone knows it, and it's CMS-neutral.
|
|
|
* Avoid CMS-specific plugins
|
|
|
* Promote the CiviCRM Contact dashboard, instead of a CMS user dashboard
|
|
|
* All forms must be managed by CiviCRM or CiviCRM extensions (ex: formbuilder, but not webform).
|
|
|
* Avoid creating CMS-specific plugins for custom code. Migrate them to CiviCRM extensions as much as possible. Reduce the quantity of custom code as much as possible.
|
|
|
* Multi-lingual - it should be possible to easily translate all content.
|
|
|
* Adding content should be easy (not require knowledge of HTML, easy to upload images).
|
|
|
* Document features - main features must have a short wiki page describing how it was built, for the next contributor.
|
|
|
* Keep it simple - minimal use of plugins.
|
|
|
* Make it easy to add blog, comments, civicamp content, but strong gate-keeping of content (request updates via the website issue queue).
|
|
|
* Identify a page/layout builder that offers fixed layouts (define a layout for content "a", "b" and "c", enforces some consistency)
|
|
|
|
|
|
# Tasks
|
|
|
|
|
|
* [ ] Blog migration (content, taxonomy, authors, comments)
|
|
|
* [ ] Theme port or rewrite
|
|
|
* [ ] Migrate users (and association of user-content)
|
|
|
* [ ] Partner listings
|
|
|
* [ ] Member listing (not launch-critical)
|
|
|
* [ ] Case Studies
|
|
|
* [ ] Make it happen campaigns
|
|
|
* [ ] Events
|
|
|
|
|
|
Custom code:
|
|
|
|
|
|
* [ ] ccrm_extensionvalidation: Extension directory: only a small parts needs to be ported, assumes Tim works on the replacement (Comex), and that it would be ready in time.
|
|
|
* [ ] civicrm_org_members: sumfields hook for member program? (only a few lines of code)
|
|
|
* [ ] civicrm_org_newsfeed: does a Views hack to generate RSS feeds (not sure if it will be easily portable, although most of the Views d8 code seems very similar to d7)
|
|
|
* [ ] civicrm_org_providers: adds badges to parters (in a custom field)
|
|
|
* [ ] civicrm_org_stats: d7 tokens for content (consider deprecating it?)
|
|
|
* [x] civicrm_org_stats: updates extension usage stats
|
|
|
* [ ] cividownload: download page, and a fundraising campaign that has long been disabled.
|
|
|
* [ ] extdir: `extdir/git-urls.json` and other services (medium-sized) - most of it should be replaced by Comex, but we may need to do more review. |
|
|
\ No newline at end of file |