โšก๏ธ Live updates comments, jobs, and issues, tagged with #frontend will update issues and activities on this page.

Issues

The last 100 updated issues.

Activities

The last 7 days of comments and CI jobs.

  • ๐Ÿ‡ฌ๐Ÿ‡งUnited Kingdom catch

    Seems like there are two issues, the original intent was what to do with the lms_lp_step_* themes and I agree that they should just be dropped. Using #item-list seems like a great solution.

    I'm very +1 to this and it's what I think we should do in this issue. We can add theme suggestions so they're easier to customise.

    Then there is the question of whether the LMS project should offer a whole-site theme so it can be more-or-less a drop-in replacement for Opigno. Maybe this should be discussed in a separate issue? The more I think about it the more it seems to me that it's not necessary and should be left in the hands of each site builder.

    I think this is worth an issue to discuss, however my inclination would be that we should try to provide UI suite components and think towards compatibility with experience builder and the theme builder that eventually will come with that, as opposed to developing a theme as such.

    Neither me nor @graber have any short or medium plans for a distribution, I think there is a place for a recipes-based distribution for Drupal LMS eventually (along similar lines to Drupal CMS), but we don't currently have a client who would need that and aren't planning to try to sell Drupal LMS as a 'product' or anything, so it's very far down the list of priorities for us. Although if someone else wanted to get that up and running it could be interesting.

Production build 0.71.5 2024