Send us your feedback

WARNING: this still need to be implemented !

You may noticed the little bubble on the bottom right of any page on the website. After promoting the website, the best thing you can do is to proofread a guide and help us improve the existing content. To reach high-quality and impact, we need the reviews of multiple external point of views. There will always be guides in construction. No matter how mature is a guide, your comments are showing us your interest in continuing to write and improve !

Examples

Here are a few guiding questions to help you think about ways to improve the content.

  • Is there any typo, grammatical issues ?
  • Is there confusing sections/sentences that would benefit from being reformulated ?
  • Is there missing context that would help newcomers with non trivial concepts ?
  • Is there missing videos or external resources to link or embbed ?
  • What kind of missing metaphors would help people get new concepts ?

Here are other questions regarding the website itself or the general content organisation.

  • How do you feel about your navigation ? Can you quickly find what you want ?
  • What about the page layout, the menu positions, the table of contents ?
  • Does the articles' layout feel to you too dense or too spaced out ? (Think about space between headings, paragraphs, code snippets, ...)
  • Is there some actions you are doing regularly, that could be simplified ?

Feedback moderation

TODO: this is the planned process but the UI and code is not there yet...

To protect the reputation of the website and avoid maintainers being attacked, every feedback follows this process:

  1. A feedback is sent and saved on the feedback server. It is not visible by anyone except its author.
  1. The queue of feedback comments is reviewed by some maintainers, when there have time.
  2. The moderation of comments will decide whether
    1. Any comment that is considered useless, violates our Code of Conduct, is off-topic or just spam, will not become public and will probably be deleted.
  3. By default they will just approve or reject the comment, approving anything useful and rejecting any hateful or innappropriate content.
  4. When approved, a feedback will become public and be visible inside the associated guide

Feedback answers

Empathy

Please bear in mind that maintainers don't owe you anything. We are all writing and improving the website on our free time, instead of spending time studying or coding on other projects. Some of the most qualitatives guides (like PCO, SYE, ASM, ...) have required over 40 hours of work along several semesters to reach their level. Using a gentle and appreciating tone really helps managing dozens on comments and deciding what to do about them.

Writing useful feedback

This section will show you how inneffective badly written feedback is. By focusing on the problme, being specific and making it actionable, you will make sure it is easy to work with for us.

The more constructive your feedback is, the is very important to help the guide maintainers triage, understand and act upon your comments.

TODO: wait a few good and bad feedbacks before

Explain your problem instead of giving solutions

If we receive a comment like

I want a Bash version of your Fish function labget.

The given solution doesn't express what is the sentiment behind this request. We can only make hypothesis: You don't like Fish ? You don't want to install it ? You don't have time to learn a new shell ? Bash is enough and Fish is too different for you ? Each of these possibility would lead to a different answer.

If the comment was explaining the problem and the context...

I use Bash all the times, I know it very well and I have no interest in switching to another shell.
I need to use labget for my labs but I see this is only working with Fish.
I don't care installing Fish but I don't want to switch to it and would better prefer using it from Bash.
Are you by any chance offering a Bash version as well ? Or is there another solution ?

On the maintainers side, we cannot and don't want to maintain multiple versions of the same code in various languages. There is a way to call Fish functions from Bash, by generating Bash wrappers. We have a page documenting this that we can use in our answer. After Fish and labget installations, this student will be able to continue using Bash and labget from Bash.

Please explain your context clearly, what is your problem and eventually what are your suggestions ?

Be specific

If we receive a comment saying

Selection: Change the /etc/hosts ...
Comment: I don't get what you are telling here.

In one scenario we agree this is poorly written and will be improved. If we think this is already good enough, we have to no way to understand why this is not clear ! Is it an issue with the idea itself ? The way it is phrased ? It doesn't make sense with another section ?

Here is the kind of specificity we are expecting you.

Selection: Change the /etc/hosts ...
Comment: I don't get what you are saying. Your mention of the Linux hosts file seems to be in contradiction of the impact of local DNS configuration, discussed in previous section. Which one is the first to apply ? Why are you suggesting changing the hosts file is better ?

With this approach, this is much easier to try to fix the issue for the guide maintainers.

Make it actionnable

When we receive comments like this

Selection: For Fedora run sudo dnf install -y bat and on Ubuntu sudo apt install bat.
Comment: What about Arch btw ?

This kind of non actionnable feedback will be ignored. If we didn't put the effort to include the command for Arch Linux (like many others: Alpine, Gentoo, openSUSE, ...), this is because we have no idea what they are. In addition, we cannot care about distributions we don't use ourselves, for which we don't have an easy way to search and test the command.

Selection: For Fedora run sudo dnf install -y bat and on Ubuntu sudo apt install bat.
Comment: Can you please add the following command for Arch Linux? I just tried it and it works.
Suggestion: and for Arch pacman -S bat

Feedback policy as of 2026-08-12

This is the copy of the feedback policy displayed when visitors opens the feedback system. We aim to create the lowest friction experience, but we need to inform visitors about feedbacks licensing, code of conduct and AI policy. This is a shorter version

This policy is integrated into the first form presented in the feedback system. It must be read and accepted directly Once the latest version is accepted, all feedbacks can be sent without having to accept it again.

As a visitor of lxup.org, you need to be aware of a few privacy and licensing principles. This takes only 3 minutes to read.

Privacy

  1. By default, feedbacks are not linked to your name or email address. And we don't store IP addresses. The website will show a unique visitor <number> and the date of feedback submission with each feedback.
  2. Some feedback categories include automatic metadata collection (like your browser version, OS version). In this case, we show you what is being sent to you can decide if you are good with it.
  3. You have the option to associate a name to your feedbacks. This name doesn't need to be real and will be publicly visible.
  4. Optionally, you can enter an email address, to receive notifications when progress is made around your comments (after their moderation). Notifications can be disabled afterwards if necessary.
  5. Email addresses will be kept private and only accessible to the server administrators for maintenance needs.
  6. To avoid the standard email/password system, you have enable you edit or delete your feedbacks (but not others'). After accepting this policy, you'll have an special account on our server. It will store unique identifiers to authenticate your browser and show a visitor number to the public. If you choose to give your name and email addresses, we will also store it.
  7. You can learn more

[checkbox] I understand and agree to this Privacy policy

Licensing

  1. [checkbox] I will only send feedbacks redacted fully by myself, without any assistance of AI/LLM (such as ChatGPT, Claude, Gemini, etc). If needed, learn more in our AI policy.
  2. [checkbox] I understand that my feedbacks are moderated, stored indefinitely on server <URL> and displayed publicly.
  3. [checkbox] I agree to release my feedbacks under the CC0-1.0 license, making them dedicated to the public domain. This makes it easy for guides' maintainers to integrate your suggestions easily.

Moderation

  1. Be respectful TODO finish this

TODO add a link outside visible under the forms, to page to write the best comments.

TODO: server URL !

Feedback system details

This section is only useful if you want to understand the

  • The feedback system will generate some unique identifiers persisted in the web browser. (The first is the counter of visitor_number like visitor 102 and the other is a random secret number like 981efe26-9717-11f1-84db-8a343fe5dafa)
  • This allows to create login-less and password-less account. These identifiers alsow allow to group feedbacks by visitors, and tell the difference between two visitors with the same name.
  • Your password-less account will be stored on server <URL>, including the unique identifiers, if provided your name and email address, the version of the accepted feedback policy and date of acceptance. At any point in time, you can choose to delete your account, change your name or email address.