How to contribute to https://blog.nowhere.moe/

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 do not accept any unnecessary technical complication, keep it concise and simplify it as much as possible. Any technical complication must be justified with clear reasoning, using graphs.

IMPORTANT PARTS OF THE BLOG FOLDER STRUCTURE :

├── assets				<--- blog assets
│   ├── css
│   ├── fonts.old
│   ├── img				<--- add your profile picture in the img folder if you want
│   └── webfonts
├── index.html			<--- main blogpost page (no need to edit that)
├── README.md
└── opsec
    ├── 0_anon			<--- template tutorial folder
    │   └── index.html
    ├── anonaccess		<--- example tutorial folder
    │   └── index.html	<--- index page of the tutorial (where steps are showcased)
    │   └── 0.png		<--- images needed for the tutorial
    │   └── 1.png
    │   └── 2.png
    ├── index.html		<--- privacy / anon / deniability tutorials index page, where they are all listed

Prerequisites:

If you want to do one of the tutorial ideas i already listed in opsec/index.html (the main tutorials index):

you don't need my approval to do it. Just check with me directly to make sure that you understand what the blogpost idea is, to avoid wasting time doing something wrong.

If you have a new blogpost idea:

Send me on chat your blogpost 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 blogpost idea is validated: proceed with below:

- fork the repository
- git clone the forked repository so that you have it locally
- go into the /opsec/ directory, and copy the "0_anon" template directory into whatever other name you want like "anontuto3"
- then edit the index.html file in /opsec/anontuto3/index.html, to contain :
	- your pseudonym,
	- the date
	- the title of the page
	- the correct blogpost writing style as explained here: https://blog.nowhere.moe/opsec/tutorial/index.html
		- 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: (see the full explanation here: 
			- 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.
	- (optional) and edit the bottom of the page to contain your links, and contact to reach out to you, and your "donate monero address"
- then create the PR (pull request), to ask me to merge your edits, and ping me about it, so i can review it, merge it and pay you in monero for it.

- /!\ not allowing any javascript, this blog will remain HTML/CSS/images only. the changes should only be Images and HTML edits.

Each tutorial can be assigned to at most one contributor, and I allow only ONE tutorial assigned per contributor at a time, i want quality, not quantity.

If you see a tutorial already being assigned to someone, either wait for that tutorial to be un-assigned (past the deadline) and then ask me to assign it to you, or go pick another one.

NOTE: If your assigned tutorial is past the deadline, the tutorial won't be assigned to you anymore, and you won't recieve any payment, it must be completed by that time. If you want to move the deadline, contact me directly explaining why.

Contributors Todolist

Each upcoming blogpost has it's own gitea issue as listed here.

To see their status in the overall opsec blog project, check out the project board here.

LICENSE

This entire blog is licensed under Creative Commons Zero: No Rights Reserved (Public Domain) Feel free to run your own blog if you want a more restrictive license.