heroicnick → credited simhag → .
We revised the list of components and decided to implement (for the start) the following elements:
- Columns
- Text
- Text / Image
- Image-Grid
- Accordion
- Testimonial
- Cta
- Jury
- Sponsors
The setup of the drupal 11 system with basic node types and taxonomy-terms and modules was implemented and can be reviewed once the staging environment ( https://www.drupal.org/project/splashawards_germany/issues/3505886 📌 Creation of staging environment Active ) is ready.
We are going to provide a staging environment to test the implementation for the drupal system and its content components. This will be replaced once the final hosting infrastructure is done. We will use the staging environment for our weekly meetings and Review.
heroicnick → credited simhag → .
heroicnick → credited simhag → .
heroicnick → credited simhag → .
heroicnick → credited simhag → .
heroicnick → credited simhag → .
heroicnick → credited simhag → .
heroicnick → credited simhag → .
I´ve tested the MR !548 and it fixes my Problem!
Because of a nesting within a paragraph I was not able to click the button for further elements due to the bug.
Applying the patch makes the UI conform to my expectations, thank you very much. I would suggest the RTBC Status.
Patch #67 also worked for me (Drupal 10.3.8)
I have added a template to the custom block and set the category of the block to system. I was also able to successfully test the functionality including the new template. I added a MR for the new block plugin implementation.
Alright, looks good to me. I merged the MR.
I created a new pull request to add the hook implementation for the help module.
I reviewed the MR and merged it.
simhag → made their first commit to this issue’s fork.
simhag → created an issue.
simhag → created an issue.
simhag → created an issue.
simhag → created an issue.
simhag → created an issue.
simhag → created an issue.
I reviewed the PR8 and can confirm that the messages are now in the untranslated version.
RTBC +1
I would suggest to use a more generic title, because other modules might also make use of the logo file
I reviewed the PR392 and can confirm that the logo is now available in the module. Im not sure if the logo.png is also needed elsewhere.
I have reviewed the PR and can confirm that the message now includes the label. (See screenshot).
Even if I agree that an ID of the view might be more meaningful, the label is definitely an enrichment for the user from my point of view.
RTBC +1
simonbitmade → created an issue.