Create friendly tips for KDE software
Closed, ResolvedPublic

Description

After some discussion, I decided to simplify and re-focus this task. Originally, I wanted to target two types of people with the same task: existing KDE users searching for quick tips and people searching for a tutorial online to solve a specific problem. For group number two, the tutorials would be used to offer KDE software as a solution to their problem and, in turn, be used to convince them to give KDE a try. Those two types of people cannot benefit from the same type of content, even if the content might overlap somewhat (e.g: both kinds of content would teach something). The first group is already familiar with KDE software and wants something straight to the point, as Paul Brown pointed out in the Promo group. In contrast, the second group of people have zero knowledge about KDE and need to, first, be persuaded to download KDE software and, second, need detailed instructions that do not fit into the concept of a tip. Trying to mix the two wouldn't work well because each public has different needs. This task will focus solely on existing users now. I might create another task in the future for the other target public, but that idea will be put on hold for now.

The problem:

KDE software usually has a lot of features not many people do not know about, and users avoid reading long and boring technical documentation to learn how to use a program.
There’s also a new influx of new inexperienced users due to the release of the Steam Deck, and those users don’t have many resources to learn how to use Plasma and other KDE software.

Promo tried making videos with tips but those usually take a long time to be made, so not many were produced.

With that in mind, creating written tips can be a nice way of increasing the amount of content we can produce, as they don't require video editing skills and can be made by anyone in the community. This should also help drive engagement on social media.

Goals:

By creating relevant content, we want to:

  • Increase awareness: Make new users aware of the features and advantages KDE software offers
  • Drive engagement on social media with content that can be quickly read and interacted with

Target public:

Users of KDE software that are still learning how to use it. This includes Steam Deck users.

Idea:

We'll be producing short tips that teach users useful or hidden features of KDE software they most likely already use. To do that, we'll focus on two types of content:

  1. Written tips in KDE Wiki
  2. Short social media posts accompanied by some text giving the tip and an image.

For tips in the KDE Wiki, we need to follow some guidelines to make more effective content to our target audience:

  1. Be short and go straight to the point: people’s attention span is short. They won’t read long articles
  2. Use friendly and informal language: this will help communicate with people without sounding technical and boring
  3. Be heavily visual by using screenshots, GIFs, or short videos
  4. Focus on common tasks users might not know how to do within KDE apps
  5. Showcase new, useful, or hidden features the competition doesn’t have (MS/Apple)
  6. Link to other tips
  7. Be shared in relevant places, like KDE/Steam Deck’s Reddit pages and other KDE social media

Discussion:

Who’s going to write the articles?

This already has an answer: Me and anyone else that feels like writing a tutorial in the promo group.

With what frequency should they be posted?

In the short term, I want to target one post per week. We should test this to find the ideal frequency.

Where are they going to be posted?

Tips on KDE Wiki should be posted here: https://userbase.kde.org/Tips

If the tip we're posting is too small (e.g: A keyboard shortcut to access some functionality), we can make those posts on social media websites themselves without needing to add them to the Wiki. As described earlier, those could simply include a small text giving the tip and an image.

There's no need for a specialized website for this task.

TODO:

  • Make Tips page on KDE Wiki
  • Select a day of the week to post

Always gather ideas of things we can post about [Permanent goal]

Guilhermems triaged this task as Normal priority.
paulb added a subscriber: paulb.Mar 24 2022, 10:14 PM

Where are they going to be posted? KDE Blog? Special page?

Wiki?

Guilhermems added a comment.EditedMar 24 2022, 10:44 PM

Where are they going to be posted? KDE Blog? Special page?

Wiki?

I don't think it would work well for a few reasons:

Wikis usually have well defined themes that can be categorized for easy navigation, but the tutorials might not follow that formula.

  • Putting them in the wiki could limit the kind of content we want to add. In the future we might want to start making posts that go beyond tutorials for specific programs.
  • Wikis usually use a more formal language and are a resource for people that need to read the full documentation about something. Including a bunch of casually written stuff will clutter the wiki with irrelevant content for the target public.

Where are they going to be posted? KDE Blog? Special page?

Wiki?

I don't think it would work well for a few reasons:

Wikis usually have well defined themes that can be categorized for easy navigation, but the tutorials might not follow that formula.

Create a category called "Tutorials" and group them under that, regardless of the apps they refer to.

  • Putting them in the wiki could limit the kind of content we want to add. In the future we might want to start making posts that go beyond tutorials for specific programs.

I don't understand this.

  • Wikis usually use a more formal language and are a resource for people that need to read the full documentation about something. Including a bunch of casually written stuff will clutter the wiki with irrelevant content for the target public.

What AAARE you talking about? Use the language you see fit, buddy.

Guilhermems added a comment.EditedMar 25 2022, 12:07 AM
  • Wikis usually use a more formal language and are a resource for people that need to read the full documentation about something. Including a bunch of casually written stuff will clutter the wiki with irrelevant content for the target public.

What AAARE you talking about? Use the language you see fit, buddy.

I think wikis are for people looking for technical information, but if you say there's no problem...

Putting them in the wiki could limit the kind of content we want to add. In the future we might want to start making posts that go beyond tutorials for specific programs.

I don't understand this.

What I meant with "go beyond tutorials for specific programs" was to create posts where the main intention isn't to make a tutorial or teach something, but to help the reader to find software solutions to their problem. Let me explain:

We make a text with the following title: "3 best free alternatives to Photoshop". This text is technically a tip (so in scope for this task), but it's not a tutorial and also won't necessarily only talk only about KDE offerings (in this case it talks about Photoshop and maybe even GIMP, but of course, we add KDE offerings in the list as compelling choices as well). See how that would feel out of place in the KDE wiki? That's why I say it could limit the kinds of posts we can make.

But if you think my concerns are unfounded I can definitely post to the wiki.

I made the first draft version of the first tutorial. This one targets the target public number 2. You can see what it looks like here: https://collaborate.kde.org/s/Jb8mXNeYcBnQXW9

Since this one targets people that don't yet use KDE software, I really wanted to make it rank well in search engines.

I wanted to put to use some SEO techniques I've been learning lately. They include repeating some keywords at the start of the text (not too much!) and using synonyms as well, adding alt tags to images, using descriptive filenames, adding a meta description, adding related links, etc...

I don't think I can use the tactics that require editing the HTML code of the page when using the wiki, BUT, that is not necessarily a problem. We don't yet know if those tutorials will generate enough engagement to justify their existence, and I'm no web developer, but I guess making a new website is not a trivial matter. With that in mind, I think it's fine if I start posting to the wiki and, in the future, if those tutorials gain traction, we can think about making them something bigger and possibly migrating them to a dedicated place. That way, I can put my plans into action.

For now, the wiki will do.

really cool, hovewer KDE Connect isn't avaiable on the Deck

Guilhermems updated the task description. (Show Details)Apr 2 2022, 6:33 PM

really cool, hovewer KDE Connect isn't avaiable on the Deck

I know. This first tutorial will be aimed at target public 2 as described in the task. The next article will focus on Steam Deck users as well.


Hm... KDE already has a page for tutorials but those are more detailed and technical.

I think I'll call the page for this project "Tips" instead, so it will go to https://userbase.kde.org/Tips

It also makes more sense since the articles I'll make will be simpler.

I'm thinking this could complement the KDE Tips task but it would be text instead of video. Maybe I should add this as a sub-task to that one. What do you think @paulb ?

For now, I'll start making the necessary pages.

Guilhermems updated the task description. (Show Details)Apr 2 2022, 10:01 PM
Guilhermems updated the task description. (Show Details)Apr 5 2022, 9:38 AM
Guilhermems updated the task description. (Show Details)Apr 19 2022, 1:19 AM

A centralised page for tips is a good idea. Maybe it would even make sense to migrate userbase articles that need to be rewritten to this new site (for better UX than the wik)

A centralised page for tips is a good idea. Maybe it would even make sense to migrate userbase articles that need to be rewritten to this new site (for better UX than the wik)

I think the wiki is still the best place for the articles in Userbase simply because they were written with the Wiki format in mind. There, people can browse stuff and find what they need, and that's what the wiki is for. A blog for tips would have a different format, where the people reading it would want more digestible, less in-depth information. It doesn't make much sense to mix the two.

Currently, I'm writing to the Wiki simply because this is a new project, so it wouldn't make much sense to have a new page now for a project that is basically in the testing phase. After we start posting, we can measure how well they are received and move over to a dedicated place.

I have four articles written. The first one is already on the Tips wiki page I created. It's still in progress because I'm figuring out how the formatting and translation work, but the text is basically ready. Tbh, I don't know if it's even worth marking it for translation since it's basically a temporary place, and translators would waste time translating something that will probably end up being moved to another place in the coming months.

Guilhermems updated the task description. (Show Details)May 11 2022, 3:53 AM
Guilhermems renamed this task from Create friendly tutorials/tips for KDE software to Create friendly tips for KDE software.May 22 2022, 11:29 PM
Guilhermems updated the task description. (Show Details)
Guilhermems updated the task description. (Show Details)

There's a new tip available!

I tried to make this as straightforward as possible. Opinions?

https://userbase.kde.org/Tips/Enable_fun_desktop_effects_on_KDE_Plasma

There's a new tip available!

I tried to make this as straightforward as possible. Opinions?

https://userbase.kde.org/Tips/Enable_fun_desktop_effects_on_KDE_Plasma

Ping!

Guilhermems added a comment.EditedJun 19 2022, 3:12 PM

Okay, I split up the KDE Connect tutorial into three tips and I also added many more. I had written some other text and I figured I could do the same I did to KDE Connect to them. This helps ensure tips are short as they should. Now we have:

1 tip about desktop effects
2 tips about Night Color
1 tip about Spectacle
3 tips about KDE Connect

Related tips are linked together.

Question for discussion:

I believe it's now time to start posting them to social media. We could either post each individual tip per week, or we could post one tip per topic (e.g. only post one tip for KDE Connect and let people find the others through the links in the text). We could also choose what to do in a case by case basis.

I won't add any more tips until I get feedback.

The tips can be found here: https://userbase.kde.org/Tips

As we are talking "tips" and not "tutorials", I would suggest you cut down the text and remove everything that is not actual tip. Everything that is not "tip" should not be in the tip.

Example of a tip written well:

Wait for the water to boil before dropping in the pasta: It will stop the noodles from sticking.

Applied to your tips, here are some changes you may want to consider introducing:

  • You can remove the introduction to the Plasma Effects tip entirely as it does not provide any useful information. The nature of effects on Plasma is made clear by the context in the rest of the tip.
  • You can also remove the introduction to the Blue Light Filter tip by changing the text:

Introduction

Eye strain and insomnia are real problems. With all the screens we’re exposed to on a daily basis, it’s hard for our bodies to adapt to all that light. Sometimes, we need to keep using our electronic devices late at night, and the blue light from our device’s screens can impact both our eyes and our sleep.

Fortunately, it’s possible to mitigate the harmful effects of blue light by enabling a blue light filter, and KDE Plasma offers one by default. In this article, we’ll explore how you can enable it.

Enable the blue light filter on KDE Plasma

On KDE Plasma, the blue light filter is called Night Color. We’ll be referring to it as such from now on.

To enable Night Color on Plasma you can do the following: ...

to

Enable Night Color to reduce the eye strain and insomnia produced by the blue light emitted by you computer screen.

To enable Night Color on Plasma do this: ...

  • You can also safely remove the introduction in the Pairing KDE Connect. The info box with the links at the top makes clear what stage the reader will be at in the chain of tips.
  • Also remove comments like "It's pretty easy to pair your devices, huh?". It is not part of the tip, provides no useful info, so it shouldn't be there.
  • etc.

You get the idea.

Guilhermems added a comment.EditedJun 23 2022, 11:20 PM

I simplified the introductions and now they are at most a line long.

  • Also remove comments like "It's pretty easy to pair your devices, huh?". It is not part of the tip, provides no useful info, so it shouldn't be there.

I don't want to remove all comments because then the text will become too technical and cold. Remember that one of the goals is to write the tips in informal language to make them more friendly and engaging. I did get rid of some comments though and I'll take care to always make them as short as possible. I hope that's okay.

You can check the same pages as last time if you want to see the changes I made. You can also click on the "History" link on the sidebar to see what was changed.

I added a picture to tips that will be shared, simplified the introductions and removed some comments. I won't remove all comments to make the text feel friendly, but I'll use them sparingly. The pictures I added are important because they'll illustrate the links to the tips in social media, hopefully they won't be a problem.

Maybe this could be the first post:

It's time to connect your devices! Learn how you can transfer files wirelessly using KDE Connect with this tip.

https://userbase.kde.org/Tips/Transfer_files_between_phone_and_PC_using_Wi-Fi

Guilhermems closed this task as Resolved.Sep 17 2022, 6:53 AM

These kinds of tips won't bring much benefit to KDE as a whole as they're already pretty common on other places (like blogs or Linux websites) and they're only relevant to people that already use KDE software. I'm closing this. Hopefully I can come up with something more solid next time.