*Hi everyone,*

*Regarding the links shared recently, it seems that the current
documentation is primarily oriented toward technical profiles rather than
the general public. This can be quite daunting for beginners who are just
starting their journey.*

*I would like to build on a suggestion I received from Richard Lewis:*

"It would be a good idea to consolidate the key information into a single
page."

*My specific proposal is to go a step further: I suggest we merge the
technical specifications with a 'getting started' guide. The goal is to
create a unified resource that serves both the average user looking for
practical steps and the technical user who needs deeper details. By doing
this, we can bridge the gap and make the information more accessible to
everyone in the Debian and GNU/Linux community.*

*I’d love to hear your thoughts on this approach.*

*Best regards,*

*Carlos*


El sáb, 9 may 2026 a la(s) 6:41 a.m., Richard Lewis (
[email protected]) escribió:

> Joost van Baal-Ilić <[email protected]> writes:
>
> > Ola Carlos,
> >
> > Since https://wiki.debian.org/es/CommandLineInterface is maintained
> using
> > the wiki system, you're very much invited to add content you yourself
> feel
> > is useful.  If people disagree, they can change your contributions
> afterwards.
> >
> > I myself feel a short list of very common commands with short
> explanation could
> > indeed be useful.  Go for it!
> >
> > Thanks for your interest!
>
> I think you're maybe not meant to edit the /es/ page as it's translated
> from https://wiki.debian.org/CommandLineInterface
>
>
> There are currently several other pages that could be usef for this - i
> spotted at least
>
> https://wiki.debian.org/ShellCommands
> https://wiki.debian.org/CommandLine
> https://wiki.debian.org/CommandsCLI
>
> and these all look mostly like they are trying to do the same thing (but
> not entirely successfully - very little useful info on some of these!) -
> perhaps they could be combined those into one, more useful, page and the
> others deleted
>
>

Reply via email to