Ablageort im Repository (GitLab): Projekt3458-OpenCulturas
Diskussionsforum (Discourse): Projekt3458-OpenCulturas
Readme: Projekt3458-OpenCulturas
Beschreibung des Projektes: Web-based content management platform software, ready for editorial and/or user-generated content such as: personal/group profiles, event locations, points of interest, reusable event descriptions, event dates (repeating dates possible), FAQ, magazine articles.
Tagging in many dimensions: common focus tags, per-type categorization, magazine columns, accessibility, trigger warnings etc. Content creation components like reusable media assets (images, video, audio, embeddable remote media, downloadable documents), galleries, press quotes, custom teaser sections, automatic teaser placement for interlinked content.
Multilingual, with publication workflows, WCAG compliant, cookie consent management, search engine optimized. Logged in users can manage personal bookmarks, publish recommendations and write comments to commentable content.
Read more about features on https://www.openculturas.org
PublicCode.YML: anzeigen
OSS Compliance: anzeigen
OpenCulturas is built as a pre-configured platform for cultural-focused communities, empowering actors in the cultural field to own their data and make their information accessible to a wide audience.
We provide a composer project to install OpenCulturas. For more information go to https://www.drupal.org/project/openculturas_project.
Q: How can I ignore patches?
A: The package which we use to patch dependencies allows to ignore patches. For more information go to https://github.com/cweagans/composer-patches#ignoring-patches.
We recommend to use https://ddev.com for development.
At the moment the source code is privately hosted and mirrored to https://github.com/openculturas/openculturas-distribution.
To create a new release on drupal.org we push the used git branch/tag to https://git.drupalcode.org/project/openculturas.
Someday when the issue https://www.drupal.org/project/project_composer/issues/3252534 is fixed we can directly work on drupal.org git repository.
`if [[ ! -h web/sites/default/settings.php ]];then cd web/sites/default/ && ln -sf ../../../.ddev/settings.php;fi`
Override values (DB etc.) in `web/sites/default/settings.local.php`
Make sure config_sync_directory points to ../config/sync
`$settings['config_sync_directory'] = '../config/sync';`
Cheatsheet:
More information about ddev cli command https://ddev.readthedocs.io/en/stable/users/basics/cli-usage/.
To update the version, sort list like dependencies in openculturas modules, run:
`ddev composer run info_file_normalizer`
At the moment l.d.o does not find the labels of field_group. Therefore we generate the strings.
`drush scr scripts/generate_field_group_strings.php`
All configuration are managed via config_devel.
Each configuration is listed in the info file of the profile or submodule.
So any new configuration needs to be added to the info file.
After that, enable config_devel and run `ddev drush cde openculturas` or `ddev drush cde submodule`.
This command updates all configuration which are listed in the info file and removes the key `_core` and `uuid` except for
views configuration. The uuid is needed because the uuid is used in other configuration as default value, without this
the default value would be not set/broken.