From @lauriii in #216 in #3111409: Add new Olivero frontend theme to Drupal 9.1 core as beta

+++ b/core/themes/olivero/templates/includes/get-started.html.twig
@@ -0,0 +1,45 @@
+ * TODO:
+ * - Move this markup into Drupal's core Frontpage Views.
+ * - Translate/localize this page for different languages.
 
Let's reference issue for this todo.

Comments

mherchel created an issue. See original summary.

mherchel’s picture

Title: [Code Review] Reference issue in todo in get-started.html.twig » [Olivero Code Review] Reference issue in todo in get-started.html.twig
Project: Olivero » Drupal core
Version: 8.x-1.x-dev » 9.1.x-dev
Component: Code » Olivero theme
Priority: Normal » Minor
mherchel’s picture

Title: [Olivero Code Review] Reference issue in todo in get-started.html.twig » Reference issue in todo in Olivero's get-started.html.twig
proeung’s picture

@mherchel Thanks for creating this issue. What's the best way for us to migrate the copy of this starter page (https://git.drupalcode.org/project/drupal/-/blob/9.2.x/core/themes/olive...) and have it made available within Drupal's core Frontpage views as well as accounting for globalization?

I can work on creating a patch that includes this copy to the content views, but I'm not sure what's the workflow is like for the localization of these strings. Any suggestion from folks would be helpful. Thanks!

mherchel’s picture

Category: Bug report » Task

As far as moving the data into Views core, I'd assume that we'd move our template into the core Views template. We can check with @lauriii on this to be sure.

I honestly have no clue on the localization process. There's a #multilingual in Drupal Slack.

The first step would be to create two issues (one in the Views subsystem, and another... i don't know where. It can start here in Olivero), and then update the code with links to the issues.

mherchel’s picture

Verified this still is not yet done.

Version: 9.1.x-dev » 9.3.x-dev

Drupal 9.1.10 (June 4, 2021) and Drupal 9.2.10 (November 24, 2021) were the last bugfix releases of those minor version series. Drupal 9 bug reports should be targeted for the 9.3.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.