Keep up the good work. Here's a few sugestions for you, so you can reach the maximum number of people:

There's lot's of information there. I'd suggest cutting it down to where everything fits in a single one of your comments. I know it's hard, but treat it like an abstract, and link to a PDF or nicely formatted web page.*

Speaking of formatting, you're going overboard with it. You have quotes that are entirely bolded. In this case I'd suggest bolding at maximum a small sentence. Even then most of the time stick to a few key words.

Other things, are your use of headers. They're way to big relative to the rest of the text. Try using a smaller size and a horizontal rule between sections.

Your citation style could also use a bit of work. I know Reddit doesn't support proper footnotes, but you can fake it using \^1, \^2, etc. Having everything at the bottom of the page really makes it easy for people to check your sources. More importantly, having the links in the middle of the page messes with a readers "flow".

* Incidentally, if you ever take Masters classes, you'll learn to hate page limits. I could easily see a professor giving this as an assignment with a 2 page limit.

While people do create complete packages with all those files you listed, you don't need to make a project more complicated than it needs to be. Sometimes, making a package with many modules, etc. is what a project requires. Other times, one or two short scripts might be all that's necessary.

I think one of the best ways to make your work more presentable (besides writing good, clean, modular code) is with a polished README. The README is the first thing anyone who clicks on a repository will see. So I would recommend learning some basic Github markdown (see https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) and learn how to write a good README (see https://github.com/matiassingers/awesome-readme for examples).

I'm not talking about a style change — I'm talking about adding features that have no affect on style but will fix broken layout in the appearance of some posts. So it will still be very much the Old Reddit style, for those people that want it. In fact, Old Reddit users will not be aware of the change, except for a few posts by new users no longer being messed up.

Even though there's been no general Reddit announcement of the new markdown features that I'm aware of, the new users are coming from Discord, I guess, and are used to using the new markdown there. Also the top Google hit for "markdown" gives the new multiline code feature.

Edit: This is what I'm talking about. Look at this post using these links to the Old Reddit and the New Reddit:

This
  That
     The other

This and\ That

I've got no evidence to support this, but Reddit may use some type of Markdown for accelerated formatting. If so, I could probably use whatever number I want and it'll format the list to start at 1 and increment. Test:

1. foo

2. foo

3. foo

4. foo

Yup, check the source of my comment and you'll see I just typed a bunch of 1s.

Take a look at Markdown. It's pretty quick to pick up and get some neatly formatted noted. I use this online markdown editor to take notes.

It happens when you use the > character before a line of text.

 

For example, if you want to produce this:

>This is block-quoted text

You type:

>This is block-quoted text

 

Alternatively, if you don't want that to happen, you have to escape the > character with the '\' character, like so:

> This is not block-quoted text

Which produces:

> This is not block-quoted text.

 

If you're interested in learning more about the reddit comment syntax, it uses a markup language called Markdown, and a good overview of that is available here.

><i>him</i>

Reddit uses markdown for formatting, not HTML. So italicizing would be have asterisks at the start of the word and end like * test * (no spaces).

Thought you'd know for future reference!

Protip: You can use markdown to format your table.

Something like this:

| Pos | Team | Pld | Pts | Potential | |-----|-----------|----:|----:|----------:| | 1 | Chelsea | 33 | 77 | 92 | | 2 | Man City | 34 | 67 | 79 | | 3 | Arsenal* | 33 | 67 | 82 | | 4 | Man Utd | 34 | 65 | 77 | | | | | | | | 5 | Liverpool | 33 | 58 | 73 | | 6 | Spurs | 34 | 56 | 68 |

* = still to play Man United

Would end up looking like this:

* = still to play Man United

/u/Belenoi made some good points; here's a few more things you should consider:

• Using read to get arguments is an ok way to go about it, but if you have the user pass the arguments as flags, it will make your program easier to use. ex. mkbash -f <script file> -p <prefix> -c <command>.
• Storing log files in /bin is a bad idea. /bin is only for executables needed in single user mode. Binaries (or shebanged scripts) should be stored in /usr/local/bin or /usr/bin. Logs should be stored in /var/log. The naming convention for log files is <program_name>.log, so in your case it would be mkbash.log.
• Only checking for a command in /bin will ignore commands from other places in the path, aliases/functions, and bash builtins. A better way to go about it would be to attempt to run the command, and if it doesn't run, continue with the script. For example <my_command> || exit 1.
• Rather than creating a new file to run the command, you could have it create a bash function or alias that can be added to your bashrc. That way you could run your script like this mkbash >> ~/.bashrc to have it add the command.
• Since you don't do anything asynchronously, the sleep 4 before trying to run the script should be unnecessary.
• Your readme should have a bit more information about your project. For example, you could have an about section, a usage section, an installation section, etc. Github uses a flavor of markdown for readme files; if you're not familiar with it, here's something to get you started.

Oh yeah that's markdown, sometimes it's confusing.

E.g. if you just put one new line (return key), it ignores that. If you want a single new line, you gotta put a double space and then the new line. Yeah that's a bit weird.

However, most of the time it's better to divide it into whole paragraphs anyway, and for that you just put 2 new lines - those will then be kept just like they look when you're writing it.

Another nice one, easy to remember and something you can use often, is to put underscores around a word or phrase to emphasize it (that gives you italics).

Because Reddit uses a form of Markdown, which manages things like bolding with asterisks, or automatically ordered lists.

Being so, it recognizes '4.' as an entry in a numbered list, giving it a 1.

Try this out: use 1. (or any other number and a dot) several times in a row, see what happens:

1. A
2. B
3. C
4. D

More info on what Markdown does (keep in mind reddit's version is trimmed down, so not everything will work the same here)

Something I can answer!

Because reddit was made for nerds back in the day and comments use Markdown syntax, which was made before twitter made hashtags a thing.

Lol, it's an internet thing. Reddit comments, and most internet text boxes with formatting support, use a formatting language called Markdown. Here's a cheat sheet

In Markdown, # means "Heading Text", and if you do # This is a title what do end up with is

This is a title.

You can readup on Markdown here.

Hey, I have not checked it yet, but if you accept suggestions, you can add a README.md file instead of a tutorial.txt and use "Markdown" to create the tutorial https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet.
That way will be more atractive when someone enters to the repo!
I have not tested it yet, if I do, I will let you know.

You can learn markdown real quick: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

After that just use something like pandoc to convert it into whatever document type you want.

Hey, thanks for your interesting questions!

• Yes, you can format your text using markdown formatting (the same concept reddit uses)
• I agree with your point of view on client-side encryption
• Thoughtplan is just a hobby for me at the moment. If the need arises to monetize (or there is serious revenue potential) I would be looking towards freemium models. I don't see any place for ads in Thoughtplan
• I am testing against the latest versions of Chrome, Firefox and Safari and I am aiming to be compatible with all modern browsers, so that includes Microsoft Edge as well. There is no mobile support at the moment but it's something I hope to add at some point
• You can nest (as you said) by Section > Document > Item. You can also create teams which can serve as an additional nesting layer (Team > Section > Document > Item). Sections are optional
• You cannot upload documents at the moment. Are you thinking of importing existing documents or just uploading other types of documents for storage?

I don't know how to do it on mobile, but in desktop you can use the Markdown format to structure your texts. Here is a fairly comprehensive cheat sheet you can use.

>How to quote comments?

You can quote a comment by highlighting the part you want to quote before clicking reply, or by typing a greater than (&gt;) symbol followed by what you want to quote.

Here's a markdown cheatsheet for more cool shit you can do.

I like to use this Markdown Cheatsheet if I need any help with formatting. Otherwise, double-space between rows to keep them from turning into a paragraph. We've all been there when it comes to the reddit format. :)

For images, imgur is your trusty friend. It's what most people here use.

And, you are not a dork. This is an adventure with lots of treasure. I totally get it. I could geek out on indie stuff all day long. :D

Reddit uses a flavor of MarkDown to format the text.

In MarkDown, you need two newlines to create a new block of text.

The reasoning behind this is not so evident because the reddit text editor "soft-wraps" your text for you, but MarkDown also lets you embed HTML in your markup. In HTML, whitespace between elements is ignored. The reasoning behind this is so that the source HTML documents are easily writeable and readable, instead of having to look at on giant line of HTML when reading or writing the source document.

HAHAHA

It's markdown language

And you need to put a line break between each element

Like so

Check out this handy cheatsheet

Maybe a bit lateral, but have you considered Markdown? You can get a markdown editor with a preview window, or you can use something like Pandoc to produce a document once the lecture finishes.

Tables are just pipe characters.

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

You can use Wordpad, or even Notepad. I like FocusWriter and ReText, depending whether I have tons of words to bash out, or a complex paper with extra stuff.

Well.. i guess it doesn't always fail....

|Ticker|Investment| |:-|:-| |BTC|$100| ||$1000| |DOGE|$10000|

Ah https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#tables

>The outer pipes are optional

Optional, but that also makes empty cells 'ambiguous' (aka can cause differences between parsers due to undefined edge cases) of course. So yeah, use outer pipes, because without them the parser needs to guess about your empty cells.

1. Jupyter cells can be converted to markdown be pressing Esc+m, so you can quickly experiment.
2. You want to use an editor instead, like VScode, but use a markdown add-on so you can view the resulting render while you're working.
3. Everything you need to know about markdown is in here https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

You can use the block code snippets and specify a language directly in markdown for syntax highlighting across a large range of languages. Take a look at this reference.

O sistema de formatação se assemelha bastante ao Markdown. Ele é usado nos READMEs do Github e meio que um jeito de converter linguagem mais simples em HTML depois.

Markdown + pandoc + syncthing + git + writely pro(android)..

http://programminghistorian.org/lessons/sustainable-authorship-in-plain-text-using-pandoc-and-markdown

and markdown

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

Here is a sample table and code:

Generated by:

| |Cancer|No Cancer| |--|-------:|----------:| |Eat Chocolate|1|101| |No Chocolate|0|100|

See this brief guide.

__getattr__ and __setattr__ can be done with:

__getattr__ and

__setattr__

The thing is that _ is a markdown formating character. This is a markdown reference for more details.

The problem with the formatting is that you aren't supposed to start new paragraphs with indentation. Reddit uses Markdown which interprets a line starting with four spaces as a code block. Here's a handy guide.

As for the actual content of the post, it was a good read. I agree, giving your feelings some actual "life" with your own type of fantasy is an integral part of waifuism. If fan fiction is your thing, try writing your own. If not, just try to imagine your life together. It's a wonderful feeling.

There is no one standard for Markdown. Each dialect supports slightly different features. You can read the original spec here and the so-called Github flavored markdown spec here and a somewhat more condensed form here. I don't know which dialect IPython uses. Reddit comments also use markdown, but they don't support all of the GFM features. Tables are supported in reddit comments, for example, but not inline images or videos.

> Edit: why does the hashtag make the text bigger?

It's called

Markdown

and it's the way you format your posts here on Reddit.

Under the text field, you should see a little link called 'formatting help' and it tells you a few basic markdown commands like how to italicize, bold, ~~strikethrough~~ and etc...

You can do some neat stuff with markdown, but I haven't tried many on reddit. There's a pretty good Write Up on Markdown here on GitHub.

Hope that helps!

Cheers!

💡 Here's a tip on markdown and reddit: reddit uses markdown and you can write up hyperlinks like so:

[Link description](link address)

i.e., [github markdown syntax](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#links)

Your welcome 🗿

I recommend for you to delete your post and then repost it with the following:

• Code you have now. (Use markdown code blocks or hastebin.)
• What you have tried to fix this.
• More specific details about your issue. (What does the vending machine do? Be as specific as possible.
• What do you mean by "and another one"? Make sure nothing is ambiguous I'm the new post, don't expect anyone to know what's going on in your head.
• State your specific problem, don't just ask "how do I write this whole thing?" We're here to help you, not write it for you. If you have more problems after your first one, make a new post instead of just making one post that encompasses the entire thing.

Also, the reason I recommend making a new post is because editing this post won't allow you to edit the title to make it more specific. Don't say "help please" in the title, give a brief overview of the problem.

Just clicked on your profile and saw this. Sorry for the wall of text you didn't ask for lol. The reason some emoticons don't work is that Reddit uses markdown for comments. This means that there are certain characters that do special things. I.e. ^ makes text small and raises it ^like ^this.

This is why ヽ( ^∀^)ノ doesn't show in the way you'd hope it would. The solution to this is in many programming languages \ is what's called an 'escape character' and cancel out the special behaviour.

So you can get ヽ( ^∀^)ノ to show properly by using \

I typedヽ( \^∀\^)ノ

There are many special characters in markdown which you can read about here. Typing the \ will prevent the special behaviour from happening on all of these characters. Something else that is very useful is typing []() to make your text into a link.

[text](link)

If you use old reddit on desktop I would highly recommend getting the browser extension RES which among many nice features gives you a preview of what you're typing will show up.

Again sorry for the wall text just thought it might be helpful to someone who is fairly new to posting reddit

yes

Reddit uses a markdown modification. It doesn't use code-fencing. (at least on old)

Using new.reddit.com and old.reddit.com sometimes render the same input differently.

I think a list without whitespace works on new, but not old.

213123 - sdf - sdf 21341

vs

213123

- sdf - sdf

21341

Also you can insert a <enter><enter> <enter><enter>

&nbsp;

to have additional spacing -- newlines alone do not, because they are truncated.

&nbsp;

Clients are fragmented (on markdown-parsing), so you'll have to assume they can bork too.

some clients even show "102" and "10^2" as the same

For a multi-line block of code, you need three backticks before and three at the end (see this, though Reddit unfortunately doesn't seem to support syntax highlighting).

+= is list concatentation in this context, so new_sentence += swear_words[swear] is equivalent to new_sentence = new_sentence + swear_words[swear]. Try printing out before and after and see what happens. Also consider this: what is [1,2,3] + [4,5,6]?

Glad you like it! I passed the enhancement ideas on to our developer.

On the last item, you can format text in most of the boxes using Markdown.

As to missing spells, if you message me those you've noticed I missed, I can add them.

EDIT

Also, most of my players tend to use Trackables for spell slots. I'd be curious to hear your thoughts on that route.

As other comments stated, you can use Markdown. There are many reference sheets that are better than the reddit linked ones since it's an actual markdown language. Here's a <strong>cheatsheet</strong>. FYI Discord supports Markdown as well.

I will say the new Reddit fancy editor makes this much easier on desktop and I did not do this on mobile.

Indent your table 4 spaces (code formatting) and leave a blank line before and after it and you should be able to get it to format readably. Like so:

1 2 3 1 0.5 0.25 0.25 2 0.4 0.3 0.3 3 0.2 0.2 0.6

Alternatively, you can make a markdown table

It's not a third party text editor. Jetpack just enables you to use markdown in the same way you would with GitHub. If you're not already familiar with writing in that style, it's actually a great skill to learn for future projects.

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

It's called markdown language. Scroll down to the Tables section here: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

Also, I've show how you format it below before entering into reddit. (Remove the leading apostrophes and single space it and it will work!)

'PLAYER|PTS|TRB|AST|STL|BLK

'-|-|-|-|-|-

'KD|28.8|10.8|7.5|0.8|2.3

'Steph|27.5|6.0|6.8|1.5|0.8

'Klay|16.0|3.8|1.0|0.5|0.3

'Dray|9.3|6.0|8.5|2.0|1.5

Markdown

Introduction

This shit is fucking lit for writing anything really. It's not even hard or anything, just requires some reading like this

Theory

~~I mean look at this fancy ass markup who needs LateX right?~~

Conclusion

1. Markdown is awesome

2. And so are you

3. Fuck yeah Expanse is renewed!

Pandoc

Pandoc can be used to convert a normal text file on your computer to a proper pdf if you use markdown.

I use the built-in bullets (asterisks *) rather than pasting my own bullets. You can click 'source' below comments to see what the original looked like.

My formatted list, when typed, looks like this:

Face

* Hard Candy's Glamoflauge concealer in Ultra Light * L'Oreal True Match liquid foundation in W1 Porcelain * e.l.f. Perfect Finish HD setting powder in Clear * Some blue cream makeup facepaint I had leftover from a costume

Eyes

* e.l.f. eyeshadow primer in Pearl * e.l.f. Mad for Matte eyeshadow palette-Holy Smokes * Wet n Wild kohl eyeliner in Baby's Got Black * Kiss eyelashes in Sultry_a * Maybelline Pumped Up Colossal Volum'Express in Classic Black

Lips

* e.l.f. Mad for Matte eyeshadow palette-Holy Smokes * Burt's Bees Vanilla Bean moisturizing lip balm

So yours was actually really close, I just replaced the bullets with asterisks and put some line breaks in :)

Edit: it's a formatting language called Markdown. Here's an example cheat sheet I use on top of the RES formatting help. It's useful because it has examples

If on old reddit or on a phone, visit this link to learn how you could increase font sizes and format your texts on reddit.

To post a picture on old reddit, go to this link and upload a picture file using the designated buttons.

On the new reddit (redesigned reddit) on desktop, you can just use the buttons at the bottom of the text box as you can in this picture.

*.md files (including README.md which is generally displayed by default) on Github (and other places) are written in markdown. You can view the source of pages like that by clicking on the raw link which shows you the markdown used to create that page. Quite a lot of that page is externally created images

Look into Markdown. You store the formatting as part of the text. For simple things like bold you'd be inserting a few characters into the matched strings.

/u/Milli63 - This is the answer to your second question:

> ...do you know how i can make the bottom box also have a background..."about" "help" etc. box

Also, I concur in that you may need some additional technique in order to conquer your CSS editing. Here are a few helpful links:

• [Customizing Sub Tutorials](/r/CSSTutorials/)

• [Reddit Sub CSS Selector Legend](/r/selectorlegend)

• [Custom Sub Flairs](/r/csshelp/wiki/userflair)

• [Customizing The Sidebar](/r/modhelp/comments/lr8bk/factrans_guide_to_a_better_sidebar/)

• Markdown Cheat Sheet

> i honestly don't know why its a thing

Reddit uses markdown for posts and comments. Tons of neat tricks available. I think all of these for example should work on Reddit.

I can't help you with the first, but with the second if you create the text in the plaintext box using Markdown, and then use the action Make Rich Text from Markdown that should help.

The correlation section was super confusing for me. X is whatever variable is listed, and Y is higher SR?

Also, here is how to format tables in markdown.

Here's a generator.

Interesting read, though, and it anecdotally confirms my personal experience playing McCree at Diamond and higher. I've noticed that my solo kills and ult kills are consistently toward the bottom-most percentiles (according to OverBuff and MasterOverwatch), but my damage dealt, obj time and accuracy is consistently near the top.

Actually, you can do it with just two spaces.
Like so.

Reddit uses markdown, although I don't know the specifics of how the backend translates everything. Many of the cheats in this cheatsheet are still applicable, though.

In markdown syntax, a single hashtag symbol (#) is for Heading 1, 2 hashtag symbols (##) for Heading 2 and so on. Markdown supports up to 6 levels I believe. Here's a markdown cheat sheet though I believe Reddit uses its own flavor of markdown.

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

No dramas at all :)

Have a look at this website, I use it in concert with the formatting tips that Reddit gives, and it's come in handy.

Plus, the formatting is a side thing to the writing, which I did enjoy anyway :)

No need to upgrade anything. Simply move over to Google Docs or Word as /u/WatchedByChickens/ mentions. Docs saves your progress with every few keystrokes. WP does not auto-save that often.

I've actually started writing in HTML markdown in my Google Doc articles. I'm trying to utilize a more future-proof writing method.

By using markdown, I don't have to manually add HTML tags. I just use an online converter and notate where I want items like images and stuff like that. Whatever's comfortable. Good luck.

> Thank you for this!

No problem.

> I actually don't use reddit much, which sounds silly but I kinda just lurk most of the time.

For future reference here's a complete Markdown cheatsheet.

> I only have high karma because of my League of Legends content I submitted for work.

Speaking of that, I heard ArchivistBecks is now working for Riot. Do have any way to check up on her? She was pretty rational before having some kind of mental breakdown back in March and going from "pretty reasonable neutral" to "batshit crazy anti" (I'm talking Geordie Tait level). I'm kind of worried about her.

I think tables/diagrams are the type of things that you just can't display well in a markup language like markdown while retaining a decent amount of flexibility, being easy to write and staying within a 80 character limit. Replicating the table/diagram geometry by displaying it with pipes/dashes/colons in the plaintext version is just too much of a pain.

I mean, look at this. That table is ridicoulusly simple but already takes ages to create/edit with the whitespace, special characters and so on. And it can't even do multiline cells. Imagine having to create this or this in markdown (or one of its variants). Impossible.

> Are you a wizard?

Not for another 22 years. ;)

But seriously, reddit comments uses markdown markup. And a new paragraph is just a double line break.

Welcome, welcome.

If you're new to reddit, may I highly recommend the reddit enhancement suite. One of the things that drove me insane when I first joined was not being able to see what I typed looked like and with RES, you get a live preview (along with lots of other cool stuff). For formatting, this cheatsheet is pretty helpful too.

Yes. There are two ways. Above, I used an in-line link. To do this, you put the Title in square brackets, then immediately after you put the url in parentheses. When you save it, the title will appear blue (see above) and be an embedded link to the url. Study this page, and you'll learn a lot of way to use Markdown in your Reddit comments and postings

Markdown is fairly easy to learn as well. Reddit uses it, and there are plenty of cheat sheets around.

Reddit uses a slightly modified version of Markdown for formatting. Putting a # as the first character on a line will render a heading. Putting two ## in front will render a smaller heading. Etc.

# Heading 1

## Heading 2

### Heading 3

#### Heading 4

##### Heading 5

###### Heading 6

In case you don't know, documentation on github (and many other places) is currently written in the markdown language (.md).

Here's a great guide on how to get started with it: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

You can also use markdown editors if you prefer to get a "what-you-see-is-what-you-get" experience. The ones I've used do require that you write in markdown, but it's valuable to learn! Once you've gotten used to it you can quickly format text. :)

As /u/your_power_is_mind said you can add images to an issue you've created on github, or upload the images to another host like http://imgur.com and then include them in your documentation.

http://daringfireball.net/projects/markdown/syntax

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

https://help.github.com/articles/markdown-basics/

Note github's markdown is a slightly different dialect.

reddit doesn't use HTML, it uses markdown: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

If you want feedback on this subreddit, you're going to need to learn to use www.pcpartpicker.com

also in the .md markdown for python code you can specify python code (3 backticks python 3 backticks) more here https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet ctrl+f python. it just looks better when highlighted

Reddit uses Markdown so you should look there if you wanna make anything pretty.

If you just wanna write a single line of code or a short inline statement, you can use `single backticks` like this: someFunction().

If you want to post a whole script, you can enclose it between a pair of three backticks.

` // This is // an example \`

This becomes

// This is
// an example

And you can even specify the language right after the first three backticks, like this: ```js

Which gives

/** @param {NS} ns */
export function main(ns)
{
    // some code
}

Also, you must have two line breaks before and after blocks of code. Otherwise it won’t work (IIRC). And it makes it easier to read.

That's probably a bug, worth reporting on the obsidian.md forum.

However you're also doing code blocks incorrectly, if I'm understanding your gif. It's backtick-backtick-backtick-newline to open, newline-backtick-backtick-backtick to close: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code-and-syntax-highlighting

To answer your questions:

• Yes, the game could help in landing internships.

• Absolutely not! Even if you don't directly land an internship from this specific project, the skills you learn will make you implement the next project quicker. You're leveling up by doing this.

• Everyone makes web projects and they all sound the same. Making an AR game is cooler. Here's what you do: take your phone camera. Film someone playing the game, and record some gameplay footage using something like OBS. Edit the videos down into short segments, maybe 10 seconds each. Upload them to YouTube. Follow these instructions to learn how to have images in your GitHub README using Markdown. Make your README read like a demo: "Can be played from any phone" (below that, link to a photo from the video of someone playing on their phone, and make it so that it links to the YouTube video of the person playing). "Collect all the coins in your environment to win" (Show the gameplay footage of collecting a coin or two). Continue until you've mentioned all of the interesting things about your game. Then link to that GitHub project from your resume. Boom! Something way more interesting than a CRUD website.

+1 for Grav. It's a simple solution that also looks good. It's been a while since I used it, but I think you might need to do some markdown to build pages, which is a lot simpler than it might sound.

Overall a great solution

Reddit uses a kind of Markdown Styled Text. Check out this cheat sheet and just try the syntax in a comment.

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

H1

H2

H3

H4

H5

H6

# H1
## H2
### H3
#### H4
##### H5
###### H6

Emphasis, aka italics, with asterisks or underscores.

Strong emphasis, aka bold, with asterisks or underscores.

Combined emphasis with asterisks and underscores.

Strikethrough uses two tildes. ~~Scratch this.~~

Emphasis, aka italics, with *asterisks* or _underscores_.

Strong emphasis, aka bold, with **asterisks** or __underscores__.

Combined emphasis with **asterisks and _underscores_**.

Strikethrough uses two tildes. ~~Scratch this.~~

>Great work! Love the clean, intuitive UI.

Thanks :)

>Is it a rest api for your node backend?

Yes it is REST with mongoDB as database.

>Also, can you (or anyone who knows) give me somewhere to start with parsing the text into quote blocks, bullet points, etc? I currently use an ad hoc solution of my own creation. Is there a library or best practices anyone would recommend?

If I got your point correctly, I think markdown is a great solution for this. For this particular app, I used react-markdown as parser but there are other libraries of course.

Standard github-markdown style, three backticks in a row to start of the code block, then three backticks on a line to end it.

Or post a Gist or use hastebin or similar.

I'm using markdown mode instead of the Fancy Pants editor. You can choose it in the bottom bar, next to reply and cancel. It allows you to use markdown, which is also used to render README.md files on GitHub.

If you don't know markdown, here's a link to my favourite cheatsheet, but I can see, that Reddit has also a wiki page for it: Markdown

It's not enough to change the format, you need to take advantage of it. Here's a pastebin with your README slightly changed. Note how you can create titles/sections using #,##,###,... or how you can use asterisks to make text bold, italic, ... There's a good list of what you can do with it here (which would be impossible with plain txt)

Styling tip: I checked your repo and noticed your README is in .txt format, not .md. Usually markdown (.md) is used for easier/prettier formatting. With txt you can't do things like titles, lists, links, etc.

Of course it's up to you but I strongly recommend using it.

You can't just color whatever you want it's code highlighting so it colors whatever it picks up as being code.

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code-and-syntax-highlighting

Hey!
No worries :) you can switch to markdown mode next time and then use one of the code blocks The problem is that the result you get back from the prompt method is a string So if you enter 10, you're not getting 10 as a number but rather "10" (as a string). So then when you add + 5 to that string, you're getting concatenation rather than addition. This means the number gets added next to it. So "10" + 5 becomes "105".

To solve this issue, you need to tell JavaScript that this should be converted to a Number, you can do so by converting the string to a number using Number.parseInt(string, 10).

Your working code becomes:

 var a = prompt('Insert number');
 a = Number.parseInt(a, 10); // convert it to a number
 if (a > 6 && a < 18) {
  a = a + 5;
 }

• Resources: how to convert a string to a number

# text

Reddit uses something called markdown to format its text. Markdown is just a way of easily formatting plain text to look cooler.

Here's a cheatsheet: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

Thanks for the help. I don't need a picture. Your word is good enough.

And, although you didn't ask for it, I'm writing down a process to attach images down below.

There's a website, imgur.com, where you can upload images for free. You don't even need an account. When the image is uploaded, you just copy the link to the image and paste it in a comment. That's all.

But if you want to format the link, you can follow this guideline.

I understand completely. I quickly moved away from LaTeX as I felt that I was getting bogged down by a lot of the syntax. I evangelized markdown to everyone in my cohort so I sent around this cheatsheet a lot. I'll add that caret has syntax highlighting for mardown which helps keep things organized visually.

Haha here's some info:

>Markdown is a lightweight markup language with plain-text-formatting syntax. Its design allows it to be converted to many output formats, but the original tool by the same name only supports HTML. https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

Fixed link: [The Bard's Tale](https://en.wikipedia.org/wiki/The_Bard%27s_Tale_(2004_video_game\))

Hint: prefix the parentheses end with a backslash or use a reference link.

Thanks for the effort, but maybe you could edit your original post ? Also, maybe you could indent it better ? Here is some guidance.

Here are a few advices, in no particular order : - Since you are a beginner, you may find easier to use function based views instead of class based views ; - You choose to inherit View but you seem to want to render a Form. You may want to choose to inherit another CBV, like FormView ; - If you want a forms.BooleanField to be submitted unchecked, you may want to add required=False ; - If you very much want to use CBV, here is a very handy link

Måske lidt skæv tekst formatering?

Reddits tekst formatering er baseret på Markdown, hvor enkelt understreg indikerer at der skal skrives med streg under. (reference)

Alternativt, hvis man bruger dobbelt understreg (__sådan her__) får man fed tekst, ligesom hvis man bruger dobbelt stjerner (**sådan her**).

First rule of thumb for freelancers: avoid content mills such as Fiverr, Workana, Nubelo, Freelancer, Upwork. They will lock your money (if any) for a month (unless you pay them for the right to cash every 15 days), they will charge you up to 40% of your income in fees (platform, withdraw, then PayPal or Payoneer, then any platform you use to cash PayPal in Argentina, such as Nubi).

Instead, try your luck offering Spanish translations for crypto projects. That's a mine gold. I've made about $1000 the first time, and while I switched to developing (which is far more profitable), I think 1K for a side job that demands one or two hours per day is a hell of a deal here in Argentina.

If you decide to try your luck translating whitepaper and other technical docs, be sure to learn at least the basics of Markdown and LaTeX; you'll use those on a daily basis.

basically upload a file to github or some other web host like imgur

the do this:

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#images

the readme.md file is a markdown file and supports markdown mark up.

its like "easier" HTML

Yes /u/Flaymlad, /u/Riorlyne is correct—all formatting is done via Markdown. This is used in Details field for word entries and on the Edit screen in the Description field and the "Notes" fields in the Details tab. All the other info is in the Help screen, too.

Jebiga. Ja pišem nešto trenutno i koristim LATEX, imam oko 35 slika za sad i radi super. Pored toga mi na pamet pada markdown, ali i to mora da se prevodi u pdf i nisam ga nikad koristio za nešto obimno tako da nzm.

On the bottom of the textbox there is text in blue that says 'Switch to markdown'. Click on that and use markdown (https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet).

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code

I think this is what you want. If you want the grey border around code type text you can do the 3 ticks then optional language name (will do syntax highlighting for that language) and then what you want inside the grey box and then end it with 3 more tick

>Ok, so would it be safe to say that the goal of a carbon tax is to make carbon emitting tech/industries unviable in the long term, thus driving companies to innovate and consumers to change their habits for greener alternatives (that we hope are coming from innovation)?

Yes, though I would also offer that innovation isn't the only means by which we can become greener. In the 1950's, the U.S.A.'s mass transit systems were systematically dismantled by auto-makers, so as to promote car sales. Now, in most places, mass transit is de-facto welfare, ie: built and maintained at taxpayer expense to support the elderly, disabled, and poor. But that's not how it has to be. Many countries boast excellent mass transit systems, making living without a car not only viable, but desirable. Hong Kong's mass transit system is actually a huge source of revenue for the enclave, for example.

>Also... How do you quote people like that on Reddit?

Reddit uses a formatting syntax called Markdown. It's got all sorts of formatting tricks you can do. For the quotes just precede the quoted line with a &gt;

That's standard markdown and apparently it's not rendering correctly for you. It's rendering fine for everyone else, I suppose, thus the downvotes. FWIW I did not downvote.

I hope you don't mind. I am still learning reddit as well. Here is something that may help with lists or tables or formatting in general: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

You can start reading about it here: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

I use with other tools like latex, vim text editor + jupyter notebook but recommend you to start with markdown first

Those articles provide some good insight, thanks.

^(Also, I think you made a small error in your link formatting. Try removing the space between the square brackets and the parentheses. )

Ah, it looks like I got used to "old reddit" being fine with rendering a space as an empty cell even in tables without the optional outer pipes, but new reddit and most markdown parsers don't.

Should hopefully be fixed?

Paste the link from http...

Or 'switch to markdown' and do this => https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#links

Many editors/IDEs for other languages come with Markdown support already included, such as Visual Studio Code, JetBrains products, etc., and support side-by-side editing/preview.

There really isn't much of need for a dedicated Markdown IDE, it is only an extremely small subset of HTML, good for easily applying some basic formatting to documentation, posts on forums, etc. The entirety of all its features can be learned and committed to memory within an hour.

There are many good little cheat-sheet Gists floating around, such as this, which even show how you can embed HTML within your Markdown.