Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On 15/01/2023 08:04, bcooks...@kde.org wrote: For blogs.kde.org, I am in two minds as to the best approach here, with Wordpress and Hugo both appearing as candidates for this site. Opinions welcome, especially if you are someone that currently uses it. I don't use this site, so I'm not gonna pi

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sunday, 15 January 2023 19:50:54 CET Ingo Klöcker wrote: > On Sonntag, 15. Januar 2023 18:34:50 CET Paul Brown wrote: > > On Sunday, 15 January 2023 16:24:48 CET Ingo Klöcker wrote: > > > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > > > For blogs.kde.org, I am in two minds as

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sonntag, 15. Januar 2023 18:34:50 CET Paul Brown wrote: > On Sunday, 15 January 2023 16:24:48 CET Ingo Klöcker wrote: > > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > > For blogs.kde.org, I am in two minds as to the best approach here, with > > > Wordpress and Hugo both appea

Re: Retirement of Capacity

El diumenge, 15 de gener de 2023, a les 7:36:03 (CET), Ben Cooksley va escriure: > Hi all, > > Since time immemorial, KDE has had a custom PHP framework known as Capacity > which we've used to build a good number of our websites. > > With the rise of Static Site Generators such as Jekyll and Hug

Re: Retirement of Capacity

Hi Ben We use https://docs.kde.org/trunk5/en/kdenlive/kdenlive/index.html and https://docs.kde.org/stable5/en/kdenlive/kdenlive/index.html in Kdenlive source code. What is the procedure to point direct from Kdenlive source code to: htt

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Thanks, but we already know what we want. Cheers Paul -- Promotion & Communication www: http://kde.org Mastodon: https://floss.social/@kde Facebook: https://www.facebook.com/kde/ Twitter: https://twitter.com/kdecommunity LinkedIn: https://www.linkedin.com/company/kde

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sunday, 15 January 2023 16:24:48 CET Ingo Klöcker wrote: > On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > > For blogs.kde.org, I am in two minds as to the best approach here, with > > Wordpress and Hugo both appearing as candidates for this site. > > Opinions welcome, especially

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Hey, Just to intervene, I think another problem is that commiting changes to any SSG though git and having to understand the stack can slow down promo's work, especially when less experienced contributors would like to help in adding content. But I know working Wordpress can be a pita for everyone

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sonntag, 15. Januar 2023 08:04:18 CET Ben Cooksley wrote: > For blogs.kde.org, I am in two minds as to the best approach here, with > Wordpress and Hugo both appearing as candidates for this site. > Opinions welcome, especially if you are someone that currently uses it. I think I'd very much pr

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Hi Paul, On Sun, 15 Jan 2023 10:21:50 +0100 Paul Brown wrote: > On Sunday, 15 January 2023 08:04:18 CET Ben Cooksley wrote: > > Hi all, > > > > For some time now it has been known to us that the upgrade path from one > > given Drupal major version to the next is usually a very difficult road >

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

Hi Ben, As the main developer of Skrooge and administrator and developer of skrooge.org (currently on Drupal), _it is normal that I am in charge of the migration_. But, I don't know Hugo and I already have other websites on wordpress, so I would appreciate if I could make skrooge.org on wordpr

Re: Retirement of Capacity

Hi Ben, jp.kde.org is already replaced with Jekyll and it no longer depend on Capacity. Best regards, Jumpei On Sun, Jan 15, 2023, 15:37 Ben Cooksley wrote: > Hi all, > > Since time immemorial, KDE has had a custom PHP framework known as > Capacity which we've used to build a good number of ou

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sunday, 15 January 2023 10:33:06 CET Ben Cooksley wrote: > On Sun, Jan 15, 2023 at 10:21 PM Paul Brown wrote: > > On Sunday, 15 January 2023 08:04:18 CET Ben Cooksley wrote: > > > Hi all, > > > > > > For some time now it has been known to us that the upgrade path from one > > > given Drupal ma

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sun, Jan 15, 2023 at 10:21 PM Paul Brown wrote: > On Sunday, 15 January 2023 08:04:18 CET Ben Cooksley wrote: > > Hi all, > > > > For some time now it has been known to us that the upgrade path from one > > given Drupal major version to the next is usually a very difficult road > > with lots o

Re: Retirement of Drupal 7/8 sites (kdevelop, skrooge, blogs, behindkde)

On Sunday, 15 January 2023 08:04:18 CET Ben Cooksley wrote: > Hi all, > > For some time now it has been known to us that the upgrade path from one > given Drupal major version to the next is usually a very difficult road > with lots of breakage involved. > The conversion from Drupal 7 or 8 to Drup