PHPackages evpp/evpp\_utdk3\_customizations - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. evpp/evpp\_utdk3\_customizations ActiveDrupal-custom-module evpp/evpp\_utdk3\_customizations ================================ Customizations for the Office of the Executive Vice President and Provost portfolio of UT Drupal Kit sites 1.0.1(4y ago)0226GPL-2.0-or-later Since Jun 2Pushed 4y ago2 watchersCompare [ Source](https://github.com/ut-evpp/evpp_utdk3_customizations)[ Packagist](https://packagist.org/packages/evpp/evpp_utdk3_customizations)[ RSS](/packages/evpp-evpp-utdk3-customizations/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependencies (2)Versions (4)Used By (0) EVPP UTDK 3 Customizations ========================== [](#evpp-utdk-3-customizations) This Composer packages provides a common set of configuration and customized functionality for EVPP sites based on [UT Drupal Kit version 3](https://drupalkit.its.utexas.edu/). ### Contents [](#contents) - [Setup](#setup) - [Current functionality](#current-functionality) - [Adding new functionality](#adding-new-functionality) - [Example: Add a new content type, "Data visualizations"](#example-add-a-new-content-type-data-visualizations) - [Deploying updates to sites](#deploying-updates-to-sites) Setup ----- [](#setup) 1. Add this package to any UT Drupal Kit 3 site via the following command: ``` composer require evpp/evpp_utdk3_customizations ``` This package will be installed to the `web/modules/custom/` directory, but should not be committed to version control on individual sites (the default `.gitignore` should ignore it). 2. After site installation, enable the `evpp_utdk3_customizations` module. Current functionality --------------------- [](#current-functionality) Functionality for this package will grow over time. This section lists its current functionality. 1. Enterprise Login integration (also requires [a request to ITS](https://drupalkit.its.utexas.edu/docs/getting_started/pantheon_setup.html#request-integration)). Adding new functionality ------------------------ [](#adding-new-functionality) The base module `evpp_utdk3_customizations` does not provide functionality on its own. Each additional functional feature should be added as as a sub-module, and installed on new and existing sites. An example follows. ### Example: Add a new content type, "Data visualizations" [](#example-add-a-new-content-type-data-visualizations) 1. Spin up a local instance of an EVPP site that uses this package. 2. Replace the github.com-based 'dist' version of this package with a 'source' based version from Enterprise Github (e.g., delete the directory, then `git clone git@github.austin.utexas.edu:evpp-web/evpp_utdk3_customizations.git`) 3. Create a new Git branch for staging the new feature. 4. In the codebase, add a new sub-module, `evpp_content_type_data_visualization` in the `modules` directory of this repository, with a standard `.info.yml` file and nothing else. 5. Enable the bare module (`drush en evpp_content_type_data_visualization`) so that it is registered in the Drupal system. 6. Use the Drupal UI to create the content type and its fields. Field machine names should be prefixed with `evpp` to prevent naming collisions. For example, a field for the visualization metadata could be machine-named `field_evpp_viz_metadata`. 7. Enable `features_ui` if it is not already enabled, go to `/admin/config/development/features`, and click "Create new feature." 8. Title the feature "Content Type: Data Visualization", with machine name `evpp_content_type_data_visualization` 9. Choose the bundle "EVPP Customizations" 10. Set the path for the configuration to be written to as `modules/custom/evpp_utdk3_customizations/evpp_content_type_data_visualization`. 11. From the selection panel on the right, select the node type that you created. You may need to explicitly select the "Field storage" config related to the content type, too. 12. Export the configuration by pressing "Write." (Verify it is located in the `config/install` directory of this new sub-module). 13. Continue to build out the content type by adding any needed templates, libraries, and assets to the module itself. 14. In `evpp_utdk3_customizations.install`, add logic to programmatically enable the new module on new and existing sites (i.e., enable it in both the `hook_install()` implementation and in a new `hook_update()` function. 15. Test the workflow by pulling the site's live database (effectively erasing your locally-staged changes) and running `drush updb`. This should enable the new sub-module, which will install the new content type. 16. Commit the changes to the branch & push them to Enterprise Github, using whatever internal review process is desired (e.g. pull request). 17. Once merged into the default branch on Enterprise Github, create a new tag (e.g. `1.1.0`) and push that to [https://github.com/ut-evpp/evpp\_utdk3\_customizations](https://github.com/ut-evpp/evpp_utdk3_customizations) . This should automatically update the information on Packagist. Deploying updates to sites -------------------------- [](#deploying-updates-to-sites) 1. For all sites that use this repository, you can now receive the pending update via Composer. Assuming the sites are hosted on Pantheon, navigate to each site's dashboard & click "Check for updates." This should detect a new version of `evpp/evpp_utdk3_customizations`, which you can apply via the dashboard and deploy up to the live environment (the update hook taking care of deploying the actual functionality). ### Health Score 26 — LowBetter than 43% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity11 Limited adoption so far Community12 Small or concentrated contributor base Maturity54 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~8 days Total 2 Last Release 1794d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/97841a43aa432072be5449d3a5a32869c123982b174cb8c1b7eb2010181e8949?d=identicon)[markfullmer](/maintainers/markfullmer) ![](https://www.gravatar.com/avatar/012956b22ca9b84819eaa90d603bb3dd50236f283dea2ea169268c8dece722c6?d=identicon)[gravelpot](/maintainers/gravelpot) ![](https://www.gravatar.com/avatar/fa3a96320e299ee08a876e9459864ddb48fbb4a5347727a0c4926227b3245677?d=identicon)[pfgutexas](/maintainers/pfgutexas) ![](https://www.gravatar.com/avatar/166b10836b4f6d015d31b89bb2681095e36396a71f383d78424724ef8d7c0fcc?d=identicon)[daddison](/maintainers/daddison) ![](https://www.gravatar.com/avatar/3ecf616f86b11edbdfcceec63369c1857581f853d61cba36a3f3ad398884afa0?d=identicon)[bjc2265](/maintainers/bjc2265) ![](https://www.gravatar.com/avatar/d2507ec4be88334a1832dc32cf225a827c742bed2ea530e7d3af8545cb324ef7?d=identicon)[marcusmarler](/maintainers/marcusmarler) ![](https://www.gravatar.com/avatar/1646022f6ab06f4b01953c4b53f04db52765fabcc1745150357a126184dbc9bc?d=identicon)[ht777](/maintainers/ht777) --- Top Contributors [![jmf3658](https://avatars.githubusercontent.com/u/34824280?v=4)](https://github.com/jmf3658 "jmf3658 (7 commits)") ### Embed Badge ![Health badge](/badges/evpp-evpp-utdk3-customizations/health.svg) ``` [![Health](https://phpackages.com/badges/evpp-evpp-utdk3-customizations/health.svg)](https://phpackages.com/packages/evpp-evpp-utdk3-customizations) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)