The command below does not update the Ports tree. It updates the package list and all the installed packages, respectively.

This command is overloaded with multiple concepts.

The pkg install drm-kmod part is about installing and configuring a graphcis driver. It also implies that an user runs Intel or AMD graphics, because NVIDIA DRM driver is provided by the separate drm-nvidia-kmod kmod.

The pkg install xorg command implies that an user is going to use X11 rather than Wayland. At the moment it is indeed the best choice for Plasma, but it may change it future.

The pkg install sddm part is installing a display manager. SDDM is supported pretty well and also has an integration with Plasma. But again, it is not the only choice and user may want to install a different DM. There is also the "startx" method of starting the graphical session, which is popular amongst developers. It might be worth documenting it too.

So, maybe these three concepts should be put outside of this article or at least separated from the "KDE Plasma Installation" paragraph, as it is not really specific to Plasma.

And speaking of xf86-input-evdev - I'm not sure if it is really required. At least the upcoming Plasma 6 already has a dependency on this package, so it can be omitted.

SDDM can also be localized with

sysrc sddm_lang="ru_RU"

Continuing from my previous comment, maybe this section should come before the "Plasma Installation"?

Alt+F2 -> System Settings -> "Appearance & Style" section.

It allows changing the wallpaper and its type, change the default fonts and DE theme settings.

According to: https://docs.freebsd.org/en/books/fdp-primer/book/#writing-style-be-clear

Write in a formal style. Avoid addressing the reader as "you".

This should apply to the whole article.

Link for "Install" chapter in the handbook.

For these applications for which we do have separate ports, add the links here.

Replace first username with username and split the second one as "user name", so it is clear the first is a parameter and the second one is not.

Link to the referred Handbook chapter.

Based on practical testing, for the graphics card of 12th-generation processors, it must be installed via ports rather than pkg, and the specific port drm-61-kmod must be installed instead of drm-kmod.

Nack. The project uses aarch64 everywhere.

Btw, i agree with you, and I strongly dislike this choice. FreeBSD/i386 doesn't even run on i386, it only runs on i686, so it should be called ia32, and armv8/9 should be called arm64. But, we have to be consistent.

pkg upgrade will also update the package list unless it has just been done fairly immediately.

Hopefully drm-kmod issue will get resolved.

Problem is, this sentence as it is now is internally inconsistent (it uses "aarch64" as the project but "x86*' unlike it). I can see the point for making it clearer to newcomers by using "x86*", but in that case it should also use "arm64". Or, stick to "aarch64" (perhaps with a clarification) *and* use Project terminology throughout the sentence.

Can we find a middle ground and explain what KDE is, why the reader would want it? For example, xfce is also a modern fully featured desktop, but they're very different.

Using consistent project terminology throughout sgtm!

Can we suggest them using graphics/nvidia-drm? When i switched to nvidia-drm, I got an extra *hour* of battery life because of working PRIME. Also, something something follow the instructions in the pkg-msg? I.e. they need to enable hw.nvidiadrm.modeset in loader.conf or nothing will work.

This may also be a better place than above to mention enabling modesetting in loader.conf, a required step.

The doc is explaining it. I think doc should teach without becoming burdensome. Alternatively, we can do something with the glossary here?
E.g. "D-Bus is an IPC(glossary link) software that allows applications and desktop components to communicate and interact seamlessly".