DDEV is the official local development tool of Drupal. And like Drupal, DDEV depends on the support of the open source community.Problem/Motivation
We need to supply a bases set of content in english. This helps a lot when onboarding other since it shows how different content types work together.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #22 | Screen Shot 2023-11-30 at 09.57.42.png | 2.75 MB | sanduhrs |
Comments
Comment #2
bbralaWork has started on this. I think I've translated about 60% right now. Work will continue.
Comment #3
kraut CreditAttribution: kraut as a volunteer commented@bbrala Still wanna to finish that alone or do we bring your current state to la_eu staging? Just ping @volkerk on Slack and provide him an new database dump to import and switch. Goal of this issue should be anyway to reach la_eu production with an English translation :)
Comment #4
bbralaIf I don't find the time tonight I'll provide the dump of my current progress
Comment #5
bramdriesenI can also help with this as I'm a Flemish/Dutch speaker 😉
Comment #6
bbralaThats great! I think the content is being loaded in a staging env right now. So when that happens i'll make sure you'll get access.
Comment #7
kraut CreditAttribution: kraut as a volunteer commentedDouble checked in the absence of @volkerk but staging has latest DB.
@BramDriesen you'll get an user account from @bbrala once confirmed.
Comment #8
bramdriesenThanks! Happy to help speed things up
Comment #9
jjchinquist@kraut
I checked the EN translations of the content. Provided a few edits. For the most part it was good.
Basic Pages:
https://stage.drupal.eu/node/149/edit?destination=/admin/content
Cases:
https://stage.drupal.eu/nl/node/214/edit?destination=/admin/content
Components pages:
Titles check, all ok
https://stage.drupal.eu/nl/node/53/layout
https://stage.drupal.eu/nl/node/4/layout
https://stage.drupal.eu/nl/node/10/layout
https://stage.drupal.eu/nl/node/8/layout
https://stage.drupal.eu/nl/node/152/layout
https://stage.drupal.eu/nl/node/54/layout
https://stage.drupal.eu/nl/node/206/layout
https://stage.drupal.eu/nl/node/11/layout
https://stage.drupal.eu/nl/node/5/layout
https://stage.drupal.eu/nl/node/55/layout - last 3 missing some content: "Portfolio: ..."
https://stage.drupal.eu/nl/node/9/layout
https://stage.drupal.eu/nl/node/27/layout
https://stage.drupal.eu/nl/node/3/layout
Events:
Checked the 3 published, ignored 5 unpublished
https://stage.drupal.eu/nl/node/207/edit?destination=/admin/content
https://stage.drupal.eu/nl/node/194/edit?destination=/admin/content
https://stage.drupal.eu/nl/node/202/edit?destination=/admin/content
News:
https://stage.drupal.eu/nl/node/215/edit?destination=/admin/content
Partners:
37 - skipped because each country will have their own partner organisations
Comment #10
jjchinquistMany of the administration strings are displayed in Dutch. Which of these steps are in scope here, and which should be moved into their own issue?
Comment #11
bramdriesenI think the language of all nodes also still need to change to EN because they are currently still set to NL (also visible in the URL of the node)
Comment #12
jjchinquistContent is not language-specific at the moment. When creating / editing content, there is no language setting. It is simply that both English and Dutch are enabled as languages for the site.
Therefore, I think the nodes are fine and just the URL-Alias needs regenerating. But I can also see the Austrian community needing to re-format all the pages anyway and set up the aliases as needed. So I wouldn't spend much time on this.
I see that EN is now the base language, so that is complete.
In my opinion, what is left for this issue is: update URL aliases and set the administration to EN. Then export the DB and commit that to the project.
Comment #13
kraut CreditAttribution: kraut as a volunteer commented@jjchinquist Thanks you very much 🫶 Fully agree on URL aliases and admin 👍
Would be great if you folks finish that. @volkerk builds DB export as CI artifact.
For la_de we aim import the DB on the 30th of November for content editing 🤞
Comment #14
bramdriesenI guess if we're really using a DB export we can delete most of those "partner" nodes which we didn't translate anyway.
Comment #15
kraut CreditAttribution: kraut as a volunteer commented@Bram Good point, but we need something for the upstream website anyway.
Best would be to translate them to some EU level partner or create boilerplate.
FYI: For the DB artifacts we'll drop users and reset the admin pass in GitLab CI
Content wise we should not have any other personal data left in the DB export?
Comment #16
sanduhrsFYI: I put some work into rebasing the setup to english yesterday.
Comment #17
jjchinquistIn my opinion, you can drop all partners. At least the AUT team has a list of partners that we would need to setup anyway, so this is just unneeded overhead. If anyone needs help at a later date, any of us would be willing to offer assistance.
Comment #18
bbralaWas just thinking to keep one as an example, it also had connected cases, and would mean you can see the overview at different places where those are shown.
Comment #19
sanduhrsI took the contents from stage and put it into a module.
Please check #3404852: Add default content for clean install from existing config
Also I updated the config export to be English first.
Please check #3403627: Rebase the setup to english as the base language
Comment #20
sanduhrsComment #21
sanduhrsYou can check the result on Gitpod
https://gitpod.io/new/#https://github.com/sanduhrs/drupal-la-de
Comment #22
sanduhrsSince the content has been committed into a default_content module in #3404852: Add default content for clean install from existing config I think this can be closed. Thanks all :)
This is how a fresh install looks now, btw:
Comment #23
bramdriesenNice! Updating credits as there was manual translation work & verification done in this ticket.