What the community is for, and what it is not for
Clarity at the start saves a great deal of trouble later.
| It is for | It is not for |
|---|---|
| Asking when one step of a tutorial will not work | Asking others to do your assignment or paid project |
| Showing what you already tried, so others can help | Posting someone else's code or data without permission |
| Discussing how to learn and in what order | Promoting your own product, service or channel |
| Reporting material that is wrong or outdated | Topics outside technology and digital literacy education |
How to ask so you get a fast answer
A question that gets answered quickly almost always contains four things. Not because of a rule, but because without them people have to guess — and people skip questions they have to guess at.
- What you are trying to do. The goal, not only the step. "I want to run this project on my own machine" is more useful than "there is an error".
- What you ran. Write out the command or the step, and say which tutorial you are following.
- What happened. Paste the error message exactly, including any code and line number. Do not summarise it — a summarised error usually loses the most informative part.
- What you already tried. This is the most frequently omitted and the most decisive. Saying you tried two things shows you are serious and stops people suggesting the same two.
One habit that changes everything: rewrite your question once you have found the answer. A short "the problem was X, the fix was Y" makes your question useful to the next person who hits it, and that is the most valuable contribution in a learning community.
The rules that apply
These are enforced, not decorative.
- Be civil to beginners. A question that looks basic to you is the question that ends someone else's learning if it is answered with contempt. We reject "it is in the documentation" as a stand-alone answer.
- Do not post anyone's personal data. Including your own. Passwords, API keys, identity numbers and screenshots containing personal data will be removed.
- Do not self-promote. Links to your channel, service or product are removed, unless you are answering someone's question and the link is the answer.
- Do not request or provide unlawful help. That includes breaking into accounts, evading licences, or distributing pirated software.
- One question, one thread. Posting the same question in many places splits the answers and makes others repeat work.
What happens when the rules are broken
There are three steps, from light to heavy: a direct warning, a temporary restriction, and permanent removal for violations that affect someone's safety — particularly posting personal data or attacking a person. Removal decisions are not debated in public, because that only humiliates someone without fixing anything.
Membership data
This section exists because the site itself tracks nothing, which raises an obvious question: what about community accounts?
| Item | How it is handled |
|---|---|
| Reading this site | No account is needed and no data is collected. There are no cookies and no analytics on this site. |
| Creating a community account | If that feature exists, the data requested is limited to what is genuinely needed, and the list is shown on the sign-up page before you enter anything. |
| Deleting an account | Any account must be deletable by its owner, and deletion must not be hidden in a menu designed to be hard to find. |
| Sharing data with third parties | Not done for marketing. If a third-party service is used to run the community, that service is named. |
How to contribute without writing anything
Not every contribution is an article. These four are far more useful than people expect.
- Report a step that no longer works, with the software version or platform policy you are running. It is the single most valuable report an educational site can receive.
- Rewrite an answered question as a short summary, so the next person finds it faster.
- Answer one question nobody has answered. A long-open question often just needs one person willing to answer it patiently.
- Show us a mistake. If our material is wrong, say which part and according to which source. We fix it and state what changed.
For anything more formal, the contact route is on the support page.
About RAJA89, and who runs this site
RAJA89 is a technology education platform. The site you are reading is the brand's official home: where we explain who we are, what is available, how the community is run, and how to reach us.
We promise nothing we cannot demonstrate, and we publish nothing you cannot check. Where a page states a figure, a price or a commitment, that statement lives on the page itself — not only in an advertisement, and not only on a page that has since been deleted.
How this site is run
- No tracking. There are no cookies, no analytics, no advertising pixels and no third-party scripts on this site. We collect nothing about you while you read.
- Reading needs no account. Every page on this site can be read without registering. There is no visitor database and no form on these pages that gathers data. An account is only needed for features that store something of yours; the registration page will be linked from the navigation once registration is actually open.
- No affiliate links. No link on these educational pages pays us a commission. If that changes, the change is disclosed where the link appears.
What we do not claim
- We are not an accredited institution. We do not issue diplomas and we do not present our material as equivalent to formal education.
- We do not promise outcomes. Learning technology takes time, and no platform can guarantee a job or an income.
- We do not replace professional help. For a legal or medical question, or a security incident that has already happened to your account, the body that can act is the authority — not us.
Who is accountable
| Maintained by | Edi Rahmadani |
|---|---|
| Role | Maintainer of RAJA89: writes, edits and answers incoming messages |
| Contact | raja89officials@gmail.com |
| Languages | English (this page) and Indonesian |