This video is very beautiful, could be use the terms and ideas for this page

Features:

Navigation (or breadcrumb) bar for URLs, allowing you to quickly navigate through the hierarchy of files and folders.

Most people probably don't think of URLs when browsing through files. Also, is that a special feature? As far as I know basically every file manager has a similar navigation bar.

Supports several different kinds of view styles and properties and allows you to configure the view exactly how you want it.

Maybe add examples (icons, detailed list) for "view styles"

Split view, allowing you to easily copy or move files between locations.
Additional information and shortcuts are available as dock-able panels, allowing you to move them around freely and display exactly what you want.
Multiple tab support

"Tabs support" instead, since there have to be multiple tabs by definition for this to be useful.

Informational dialogues are displayed in an unobtrusive way.

Is that a feature that differentiates Dolphin from other file managers? In my opinion this could be dropped.

Undo/redo support

Rather minor.

Transparent network access through the KIO system.

Reword as "Easily access remote file shares as if they were local through the powerful KIO system" or similar ("network access" is quite abstract)

Features that could be added (needs rewording):

• Content previews for a myriad of file types
• Plugin system
• Browse .zip files as if they were normal folders
• Extensive search functions based on Baloo
• Tag system
• Integrated terminal

Adding a few more screenshots would certainly be good, e.g. one with split view, one with Konsole open and one with multiple tabs. The current screenshot is also really old according to the application icon at least, so replacing this one with a similarily "simple" one could also make sense.

In T13595#239527, @angelacunha wrote:

This video is very beautiful, could be use the terms and ideas for this page

Very good idea :) (kde.org/applications doesn't support video yet but the support could be easily added)

Improving https://kde.org/applications/en/dolphin is really all about improving Dolphin's AppStream metadata, which is a pleasantly small and impactful task since that metadata gets consumed and displayed in lots of locations.

Were you thinking we could additionally have a https://dolphin.kde.org/, like for example https://konsole.kde.org/? That would be the place for richer content.

https://dolphin.kde.org/ would be nice but very low-priority. I know there is already plenty of work on the table for the websites people ;)

In T13595#239806, @ngraham wrote:

Improving https://kde.org/applications/en/dolphin is really all about improving Dolphin's AppStream metadata, which is a pleasantly small and impactful task since that metadata gets consumed and displayed in lots of locations.

Were you thinking we could additionally have a https://dolphin.kde.org/, like for example https://konsole.kde.org/? That would be the place for richer content.

I would first look at improving https://kde.org/applications/en/dolphin, by for example adding a video, adding more screenshots and improving the text before looking at creating a completely new webpage. A new webpage means people will need to maintain it and in my experience this doesn't scale well :(

@thiagosueto I know you were interested in improving the AppStream description, would you like to help with Dolphin?

Yes, I can think of something for the appstream summary.
Currently, it's "File Manager", the same as the .desktop GenericName. GenericName is fine since it's what's shown in the menu and the XDG specs recommend it to be concise, but the appstream summary is a good venue for promotion and can be longer (like one line) as it's shown in Discover.

What I've found that works is initiating with a verb, following the recommendation that a good description should describe what it does instead of what it is. It's also possible to briefly mention what it's for and then go on explaining what it does. Some preliminary examples:

"Manage your files with featureful navigation and plugins" <- sounds a bit bad to my non-native ears, not sure

"Extensible file manager with dual panes and built-in terminal" <- perhaps sounds like it's always dual-paned, not the case

Something like that, since IMO the three most interesting features it has by default are its configurability/plugins, its dual panes and terminal. Most file managers don't have those.

+1 or -1 on any of those two? Opinions on how to improve those?
I'll be sending a commit for that soon (a few hours)

Find, preview, rename, move, copy -- all things I do with Dolphin almost daily.

Beautiful, powerful and flexible are how I would describe Dolphin, just like real dolphins.

Details like naming Baloo should not be in a description for users IMO.

Words like "featureful" and "extensible" make my brain shut down.

Oh, now that I noticed: it's about the description, not the summary. (Though I will send a commit for the summary too)
I haven't actually started working on the descriptions, mostly summaries.

So the current appstream description is:

"Dolphin is a lightweight file manager. It has been designed with ease of use and simplicity in mind, while still allowing flexibility and customisation. This means that you can do your file management exactly the way you want to do it."

Should we follow the template proposed in: https://phabricator.kde.org/T12811#223307 ?

In T13595#239954, @valorie wrote:

Find, preview, rename, move, copy -- all things I do with Dolphin almost daily.

Beautiful, powerful and flexible are how I would describe Dolphin, just like real dolphins.

Details like naming Baloo should not be in a description for users IMO.

Words like "featureful" and "extensible" make my brain shut down.

Hello Valorie, I agree that featureful and extensible are quite technical, and that baloo shouldn't be mentioned, but I'm not really sure about the first two. I personally think highlighting unique things rather than common functionality works better. Pinging @paulb for an opinion on this, although he should already be subscribed

I think you may be approaching this from the wrong angle. Instead of starting with the web page, I think you should start with what is the essence of the product and build up from there.

I will tell you in a sentence less than 10 words long what it is for me and then you can see if you agree or would like to write your own short description:

Dolphin is the gateway to all files and folders.

Once you have the essence, you can derive other things, like how to describe it in function of it use:

Use Dolphin to view, open and save all your files and folders on your machine, local network or the Internet.

And you can also derive the texts, the media, the general look of your web page, etc.

if you don't start with the essence, it may happen that you end up with an unfocused web page, with a mish-mash of content which leaves the reader confused.

P.S.: By the way... Where did the name "Dolphin" come from? Is there a story to that? If there is a story, some kind of metaphor, like, I don't know, you can swim out into the seas of you filesystems with Dolphin, then we may have another interesting angle we can consider. Or is it just that the original developer really liked cute cetaceans?

Personally I liked Paul's suggestion (at least for the appstream summary) as it's fully neutral and descriptive, and I could shorten it like so:

• Use Dolphin to view, open and save your local and remote files.

(But it might be an excessive cut on my part)

But following what Valorie mentioned:

• Find, preview, rename, move, copy your files. <- General file management
• Beautiful, powerful and flexible file manager. <- All three things at once

And noting what Paul mentioned:

• Dolphin is the gateway to all files and folders. <- Main means to access, enablement
• Use Dolphin to view, open and save all your files and folders on your machine, local network or the Internet. <- Both local and remote

And considering what I'd think of Dolphin:

• Dolphin makes navigation **optimal*. <- Improved workflow
• Dolphin gives you easy access to all your files. <- Accessible

Let's also take note of how Dolphin is depicted in the wiki/docs:

• The dedicated file manager focusing on usability.
• Designed with usability as a primary focus.
• It has been designed with ease of use and simplicity in mind, while still allowing flexibility and customization.
• It aims to improve usability at the user interface level.

Then we have several possible approaches:

• Navigate local and remote folders with ease <- Ease of use, optimal
• Beautiful file manager to browse local and remote files <- Emphasis on looks
• Find, open and manage your files with elegance <- Easy to do tasks while also aesthetic
• Access your local and remote files with this flexible file manager <- Focus on power users
• A file manager to meet all your file management needs <- Meets all cases, simple-by-default-powerful-when-needed

Considering the docs, maybe we should focus on the term "usability" and go with that primarily?

As for the description, the current one is:

Dolphin is a lightweight file manager. It has been designed with ease of use and simplicity in mind, while still allowing flexibility and customisation. This means that you can do your file management exactly the way you want to do it.
Features:

• Navigation (or breadcrumb) bar for URLs, allowing you to quickly navigate through the hierarchy of files and folders.
• Supports several different kinds of view styles and properties and allows you to configure the view exactly how you want it.
• Split view, allowing you to easily copy or move files between locations.
• Additional information and shortcuts are available as dock-able panels, allowing you to move them around freely and display exactly what you want.
• Multiple tab support.
• Informational dialogues are displayed in an unobtrusive way.
• Undo/redo support.
• Transparent network access through the KIO system.

It's actually pretty good already IMO.
Suggestions:

• Remove breadcrumb? Personally I'm not sure what's meant there
• I'd put split view and add built-in terminal closer to the beginning
• Following what Valorie said, maybe worth removing mention of KIO? It's not like Nautilus, Nemo or Thunar promote their internal tooling either. It could have its own section on the website, for instance

So, adding some more stuff since there's been several improvements these last two years:

Dolphin is a lightweight file manager designed with ease of use and simplicity in mind, while still allowing flexibility and customisation. This means that you can do your file management exactly the way you want to do it.
Features:

• Navigation bar for URLs, allowing you to quickly navigate through the hierarchy of files and folders.
• Support for Undo, Redo and Folder History.
• Support for several different kinds of view styles and properties and allows you to configure the view exactly how you want it.
• Split view, allowing you to easily copy or move files between locations.
• Multiple tab support.
• Additional information and familiar shortcuts are available as dock-able panels, allowing you to move them around freely and display exactly what you want.
• Easily share your folders to other computers on the same network.
• Fitting for both keyboard-driven and mouse-driven workflows.
• Informational dialogues displayed in an unobtrusive way.
• Downloadable services to improve usability.
• Full integration with the Plasma desktop, including Activities.

Opinions? +1/-1 ?

The additional features I have mentioned in T13595#239528 are probably more advanced, but I would still consider including them since your casual user will not see the Appstream description at all. Mostly users who are looking for a better file manager will encounter the text we are working on, and this user group is probably more knowledgeable than the average.

Use Dolphin to view, open and save your local and remote files.

I think this is the best starting point. The first thing the visitor should read after the word "Dolphin".

I also agree with your description on how you would proceed through the page. There may be some tweaks along the way, but your layout for the text contents looks very solid to me.

+1

In T13595#240095, @xyquadrat wrote:

The additional features I have mentioned in T13595#239528 are probably more advanced, but I would still consider including them since your casual user will not see the Appstream description at all. Mostly users who are looking for a better file manager will encounter the text we are working on, and this user group is probably more knowledgeable than the average.

A compromise would be to put these features later in the page. I would suggest starting with the most common, most basic features and uses first, and then gradually progress to more niche and specialised.

I would suggest using 3 or 4 long paragraphs instead of a bullet point list. A simple listing of the features is not very attractive and for example instead of saying that there is a tab support you could say: "Dolphin contains many productivity features that will make your life easier in many situations. The multiple tabs and split view features will help you navigate multiple folders at the same time and easily drag and drop files and folders between the open tabs to move them."

In T13595#240102, @ognarb wrote:

I would suggest using 3 or 4 long paragraphs instead of a bullet point list. A simple listing of the features is not very attractive and for example instead of saying that there is a tab support you could say: "Dolphin contains many productivity features that will make your life easier in many situations. The multiple tabs and split view features will help you navigate multiple folders at the same time and easily drag and drop files and folders between the open tabs to move them."

Oh yes. The lists would have to be developed into narrative paragraphs and be peppered with examples of usage to keep things clear

https://invent.kde.org/system/dolphin/-/merge_requests/73