Drupal Design Module Design - NCIOCPL/cgov-digital-platform GitHub Wiki
Each module should contain only the functionality necessary for providing a feature to the site. A feature could be a content type, or a shared element such as site hierarchy. It is important that we keep these components separated as some sites may not need all the functionality and we need to be able to enable or disable those modules without causing other modules to fail.
A modules should follow the Drupal standards for a folder structure.
Module | Description |
---|---|
cgov_core | Key module containing global shared configuration (e.g. workflow) and node specific configuration (shared field storage, display modes, etc) |
cgov_media | Key module containing media specific configuration (shared field storage, display modes, etc) |
cgov_article | Article Content Type |
cgov_home_landing | Home and Landing Page Content Types |
cgov_blogs | This contains blog posts & series and all the functionality around them |
cgov_factsheet | This contains the factsheet, it is also TBD depending on requirements and if it can merge with article. NOTE: This may be cgov only, or it may go into core. |
cgov_infographic | Infographic |
cgov_events | event content types, and whatever they may need |
cgov_biography | biography content type |
pdq_core | cgov_core |
pdq_cancer_information_summary | |
pdq_drug_information_summary |