Thursday, 24 February 2022

Markdown

OK, it looks like this wordpress editor automatically interprets *Markdown*… at least I think it does. **Sometimes.** Well, maybe only for headings? Or things that are on their own lines?

Things I can do

create headers with # or ## or ### …
create a block quote with >
create a list with * or 1, and indent it with a space
create inline code using back single quotes` (NB. the backquotes behave oddly, but work)
create a horizontal rule using —

Things I can’t do

create inline emphasis using asterixes
create inline highlights using =’s
create inline code using back single quotes
create a horizontal rule using ###
create a link using this syntax: [a link to my site](https://tomeri.org)

But let’s make sure the things I think I can’t do are not showing up when published

create *inline* **emphasis** using ***asterixes***
create inline ==highlights== using =’s
create a link using this syntax: [a link to my site](https://tomeri.org)

Things I’d like to be able to do

Create my own .css styles. I can see where to plug in the style names on the left, but where do I define the css styles?

Next Thing

The next thing I want to do is to learn more about git and how it is used for version control. In particular, there are people who use git for non-coding tasks, such as writing, so I’d like to see if that makes sense

After that, Jeffrey recommended I look at Visual Studio from Microsoft which could prove very helpful in (1) detecting errors, and (2) suggesting what code to write. He gave me a demo where he wrote a comment about what the code was going to do, and the editor supplied the actual code (by doing matching from within github).