I would really love to see it too and I think I will anyway need it at one point, but I don't have the time and any experience with vuejs prerendering or server side rendering. If you would like to contribute, I could guide you around the current horrible beautiful code. It shouldn't be too difficult to do since the entire data structure is already stored in multiple json files.

Increased difficulty, maybe yes, but also increased "wow" effect for users when done right. In terms of getting SEO to properly work with SPAs and VueJS in particular, maybe check out https://dzone.com/articles/how-to-make-vuejs-website-seo-friendly
I have quite a bit of experience with VueJS, vue-router and vuex and never did I have serious issues with SEO thanks to methods described in the linked article. In my opionion it's definitely worth investigating.

@joricke I had a similar idea and a very WIP prototype using VueJs. But one of the drawback of using a web application is that it is more difficult to get good SEO. kde.org/applications is responsible for 44% of the traffic on kde.org and I don't want to affect this number.

Just for reference, the repository has been already created and it is being worked on at https://invent.kde.org/websites/aether-sphinx

Just a quick idea: how about recreating the Discover interface as a SPA and using that for kde.org/applications?

Proposal plan of action: :D

+1

I will probably add one or two more sections about Plasma mobile and Kirigami/Framework or a section linking to k.o/products, so it's not final yet.

@skadinna Help with the text is very much appreciated. I will probably add one or two more sections about Plasma mobile and Kirigami/Framework or a section linking to k.o/products, so it's not final yet.

@skadinna Well, I am not a lead dev here so I can't really say if this is "final" :)

In T11714#202597, @ognarb wrote:

@mglb

@ognarb @vladimirmikulic That latest version looks really great!!

Looks good!

I worked a bit more on the homepage today. Implementing the application grid with screenshots will be a bit difficult (since all screenshots have a different format). So I will keep the same layout as in kde.org/applications for the moment.

actually let's just do the monthly updates on Dot, that seemed to work well

+1 from my side too ;)

+1

:) nice!

🎉 it works:

Ok, the .htaccess was actually not generated by Hugo but located in the static directory. I pushed to the server let's see if its work. ;)

Is there no way of getting Hugo to append given content to the .htaccess it already generates?

Hugo already generate a .htaccess in public, so this configuration need to be added in the apache conf :(

Christoph is correct here, our systems permit the use of .htaccess files, so you should be able to use the Apache Rewrite module without anything being needed on our side
(Note that RewriteBase will probably not be required)

kate-editor.org should have the module enabled and you should be able to just add some .htaccess with such rules to the hugo static files dir.

@cullmann thanks for the hint, I come up with this 404 handler written using mod_rewrite.

Hmm, beside that, can one not simply fix that by using a 404 handler that does the redirect? I did that once for the AbsInt page, just rewriting the url to the generic english page if the original url ended up in 404.

Too bad that partially translated stuff doesn't work :/
I only read a bit in the above thread on discourse: is there actually a real bug report that requests support for this?

Ok I was able to work around some of the limitations of Hugo. I added a redirection in javascript, the user experience is not very nice since we need to wait at least 5 seconds before being redirected. For example https://kate-editor.org/uk/build-it/

I added a language picker in kate-editor.org and I have bad news, hugo doesn't support partial translated website. Either the entire website is translated or it's not and a lot of dead link are created, because Hugo doesn't provide any fallback to the default language.

@ognarb, @simonkr: Thanks for the infos!
If you're busy with other stuff, I can relate. Don't feel sorry, I'm grateful that you help us out ;-)

@ognarb I agree, we should display applications in the homepage differently. Your mockup is great(better than mine), I could implement it in the applications section instead of the current one.
I would also crop them, make consistent spacing and link them to corresponding pages as @KonqiDragon already ordered :)
What do you think?

Hello @ognarb and @johanneszarl !. Sry, that i stoped working on the KPhotoAlbum Website!. But i didnt have much time because i'm in education (I'm 18). I think i need nothing @johanneszarl

Hello @KonqiDragon, this is just a mockup and not the final product. And I wanted to propose something a bit different about how we display the application list in the homepage, and before fighting with the CSS I wanted to see if it's a good direction.

@johanneszarl I think its almost the new website is almost done, I just need to fix one bug in the theme. Not sure I can finish it before the end of next week. Sorry for the delay, I'am quite busy with life and other KDE related stuff :(

In T11714#203285, @ognarb wrote:

I played a bit with the application list and I tried including a screenshot of the apps. See https://kde.carlschwan.eu

One problem is that some screenshots contains white border

@simonkr: Just checking in on this - is there anything that you need from us?

I played a bit with the application list and I tried including a screenshot of the apps. See https://kde.carlschwan.eu

In T11714#203219, @vladimirmikulic wrote:

@mglb You didn't read my previous reply. As I said this is not the final version, the text is a placeholder, don't you all see lorem ipsum???

@mglb You didn't read my previous reply. As I said this is not the final version, the text is a placeholder, don't you all see lorem ipsum???

In T11714#203207, @ognarb wrote:

In T11714#203147, @KonqiDragon wrote:

In T11714#202597, @ognarb wrote:

@mglb

It's beautiful, but not perfect.
As a guest, i see "Read more" buttons near different products, but i'm not interested to read it because it's hard to understand what it is.
Also i think it's kool to giving a different backgrounds to each selections, as @mglb said.

I think it makes only sense to have different backgrounds color, if there is a meaning behind it. For plasma desktop they were some distinct section with each a different wallpaper. In this case, I see less a need for it.

@ognarb I couldn't agree more :)

In T11714#203147, @KonqiDragon wrote:

In T11714#202597, @ognarb wrote:

@mglb

It's beautiful, but not perfect.
As a guest, i see "Read more" buttons near different products, but i'm not interested to read it because it's hard to understand what it is.
Also i think it's kool to giving a different backgrounds to each selections, as @mglb said.

In T11714#202597, @ognarb wrote:

@mglb

In T11714#202597, @ognarb wrote:

@mglb

My updated variant:

Translations with Hugo and po4a works 🎉 See https://kate-editor.org/about-kate.uk/ or https://kate-editor.org/about-kate.pl/

What do you think about giving each section different background? It would separate them and make clipped images (like kirigami one) look better.

The current look of the website is much nicer with white colour as the background :)

Thank you. Looks good!

@mglb

@vladimirmikulic can you put screenshot here?

Hmm, I guess I know how to do it better

Pictures dominance to the detriment of the text information is an anti-pattern of current web design because of which visitors for a long time can't understand where they are and what is this site about.

One problem with your mockup is that it doesn't have any pictures

Thanks for this amazing work, I really like it.

I am glad to hear that :)

@vladimirmikulic Thanks for this amazing work, I really like it. This is a huge improvement to the current layout.

Add a https://www.kdevelop.org to redesign list, it looks like a KDE style but it's have a differents from https://konsole.kde.org and https://choqok.kde.org, it would also be cool to provide in Download snap and flatpak links.

My variant: https://phabricator.kde.org/M157

@ognarb Here it is https://invent.kde.org/vladimirmikulic/kde-plasma-homepage
Feel free to suggest improvements :)

Another website which could make use of this is docs.plasma-mobile.org.

@ognarb Will do, thanks :)

@vladimirmikulic The best is that you push to a new project https://invent.kde.org/projects/new. And after that give me the link to repo, so that I can test ;).

@ognarb Are you going to set up a repo at https://invent.kde.org/websites? I need to push somewhere.

I created a repository and moved one article to it: https://invent.kde.org/carlschwan/kde-sysadmin-doc-kde-org

nice :)

WIP see invent.kde.org/websites/aether-drupal7 and test version: https://akademy-dev.kde.org/.

Same with games.kde.org:

I think we should redirect

@ltoscano I added the StaticMessages.sh script. It should now works ;)

As I mentioned, you need to create a StaticMessages.sh file in your repository, which expose the two twin functions (export_pot_dir/import_pot_dirs if you deal with multiple pot files or export_pot_file/import_pot_files if you have just one), following the example of websites/docs-krita-org, plasma-browser-integration or other projects (kdeconnect-android, for example).
The only thing I can do on the translation side is to enable the extraction for that repository, but you need to write that script.

@ltoscano I merged the change in the kate-editor.org repository. The https://kate-editor.org/about-kate/ page should now be translatable. Can the Localization team do the necessary scripty change?