- Issue created by @Grienauer
- 🇦🇹Austria a.milkovsky UTC +2
I installed the la_eu distribution locally. First impressions:
Setup:
- Tthe setup process is not properly described. The readme needs some updates and clarifications.
- It is not clear how to contribute and separate the la_eu code from our custom code. The project It is not a distribution, but basically a snapshot of the entire project. There is an open issue for this https://www.drupal.org/project/la_eu/issues/3414966 🌱 Define contribution process Active
Functionality:
- looks fancy
- There is not much custom code in modules. The theme is very customized though
- available content types:
- basic page - used for simple pages like Impressum, AGB.
- Case - case studies/projects. Uses Paragraphs.
- Component page - marketing pages with a lot of layout components. Uses Layout builder
- Event
- News
- Partner - companies/agencies that are sponsors. Also they can be referenced in Case studies.
Migration thoughts:
- the available content types do cover our needs. we currently have: Article, Page, Project, Veranstaltung, Organisation.
- He have some legacy content types, that we should remove/merge: Blogeintrag, Link, Nachbericht, Ort, Panel, Presse, Slideshow, Sponsor, Webform
- it should be easy to migrate all the data. All the marketing pages ("Component pages") I would create from scratch.
Concerns:
- Inconsistent layout implementation: Why was they layout builder used for Component pages but not for Case pages? Paragraphs are used for Cases instead.
- As mentioned above, we should find a way how to separate our custom code from la_eu.
- 🇦🇹Austria Grienauer Vienna
Thank you for your findings! a very great start and check, so we know what we need to do!
about your concerns:
inkonsisten layouts. I think no user can add pages. but a user can add cases. paragraphs are more easy for users. and layout builder is more for admins. for me it makes sense, why it is done like this, but would be good to discuss it further.
custom code, yes this is an issue, and should be discussed upstream!