forked from nihilist/blog-contributions
updated readme
This commit is contained in:
parent
f851765b10
commit
2319cf369e
33
README.md
33
README.md
@ -1 +1,34 @@
|
|||||||
# How to contribute
|
# How to contribute
|
||||||
|
|
||||||
|
## If you want to edit one of my existing blogposts:
|
||||||
|
- fork the repository
|
||||||
|
- edit what you want to edit, from the forked repository
|
||||||
|
- create a PR, and wait for me to merge it. (feel free to ping me on matrix about it)
|
||||||
|
|
||||||
|
## If you want to create a new blogpost:
|
||||||
|
yes, i pay in moneros, for well made, complete blogpost contributions (let's say between 10eur and 50eur per blogpost, depending on the complexity)
|
||||||
|
Sidenote: i will not accept any unecessary technical complication, keep it concise and simplify it as much as possible.
|
||||||
|
```
|
||||||
|
prerequisites:
|
||||||
|
- if you have a new blogpost idea:
|
||||||
|
- send me on chat your blog idea, and tell me where exactly it's supposed to fit in the blog. (i want to keep a coherent order in my tutorials, let me validate your idea, before actually starting)
|
||||||
|
- once your blog idea is validated: proceed with the below
|
||||||
|
|
||||||
|
- if you want to do one of the tutorial ideas i already listed in anon.html (the main tutorials index), you don't need my approval to do it,
|
||||||
|
- just check with me directly to validate if you understand what the blogpost idea is.
|
||||||
|
|
||||||
|
- fork the repository
|
||||||
|
- go into the /servers/ directory, and copy the "0_anon" template directory into whatever other name you want like "anontuto3"
|
||||||
|
- then edit the index.html file in /servers/anontuto3/index.html, to at least contain :
|
||||||
|
- your pseudonym,
|
||||||
|
- the date
|
||||||
|
- the title of the page
|
||||||
|
- a brief description at the top detailing what you're going to showcase, and why it's important
|
||||||
|
- contextualize what you want to showcase whenever needed, as part of explaining WHY it's important
|
||||||
|
- then showcase each step to get there:
|
||||||
|
- state what must be done, and how
|
||||||
|
- show the commands (copy paste into the <pre><code class="nim"> cmds(multi lines) </pre></code> blocks)
|
||||||
|
- if there's any GUI to showcase, use a screenshot software like flameshot to showcase what must be done using arrows
|
||||||
|
- conclude the tutorial stating what the user has accomplished at the end.
|
||||||
|
- then create the PR (pull request) and ping me about it, so i can review it, merge it and pay you in monero for it.
|
||||||
|
```
|
||||||
|
Loading…
Reference in New Issue
Block a user