towerofnix / blog Goto Github PK

Otherwise nobody will know they exist!

Math is fun; it should be easy to use it in my posts.

(This would ideally be for a post on explaining some crazy fraction math magic-but-not-actually-magic.)

Downloads for .kra files are registered as viruses by McAfee

Honestly I'm not even sure if the bold font for content text is loaded yet..

Part so there's something to sort indexes by (other than alphanumerically), and part so people can see when posts were made.

To go with the whole idea of "double quotes is for things that are read by humans; single quotes for everything else".

Correct example:

title: "Rewrote it Again"
permalink: '3-rewrote-it-again'
date: {m: 4, d: 14, y: 2017}
categories:
- 'text'
- 'blog-dev'

Note the title entry is double-quoted while the permalink and categories aren't.

Probably inside of the "meta" section (the thing below every post that includes the timestamp.. maybe the timestamp itself could be a link?).

This way, people can view post sources without having to go to the blog repository on GitHub.

Just so that people can go to liam4.github.io/blog and/or future domain name and see if there's a new post right away. Since there's no RSS feed – and RSS/etc feeds are way outdated, anyways!* – people need an easy way to see new posts quickly.

^{*don't kill me}

So that people can go to, e.g, archive.html#7-quick-update to jump to the "Quick update" table row. Might be handy for directing people to specific periods in which I post about one topic a bunch in a row. To be fair, there's also categories for that; but this shows the post in the context of all other posts. (Pluuuuus this would work for other archive pages, too; not just all.html!)

Maybe also buttons that relate to categories, e.g. "next in art" / "next by date". (Based on first category? Or "Next in [development], [text-based posts]"? Or maybe combine it all together, e.g. "Next [by date], in [development], [text-based posts]"? Or just "[Next] (in [development], [text-based posts])"?? Planning features is fun! 🎉)

May as well. Sort of a perpetual issue.

(Is the "help wanted" tag appropriate here? 🙃 )

Which leads to very bad things happening, since 10 is apparently immediately after 1 and before 2. Yay!

The date column is too small. Like I said, stupid issue. Maybe it's possible to set a minimum width on table cells? If so, would I need to apply that to every cell under that column, or could I maybe make a header row with that minimum width?

I don't know what the specific format would be since I have no idea how YAML works, but if post metadata is written in YAML there's no reason for the category description file to be a JSON file.

If I was to use this blog engine, where would you prefer the credit to be and what exactly would you like it to say?

It's already bad enough that the "static" folder is there (and everything else specific to my blog, tbh, haha - should be on a separate branch), but putting the site folder on the master branch is just silly.

I wonder if I could just .gitignore it?

This was generated, at one point..

    <meta name='twitter:description' content="A fraction is sort of like a number made of two parts. For example, we might
    have a fraction made of the numbers 1 and 2, and we would write that as
    
      
      \frac{1}{2}
      
      
      
      
      
      
      
       
       
      
      
      . We could have another fraction
    made of the numbers 7 and 9, and that would be written as
    
      
      \frac{7}{9}
      
      
      
      
      
      
      
       
       
      
      
      .">

Yeow!

Not sure how to do this. Oops.

Installing dependencies works with yarn but NPM is a bit more standard and useful.

..to be saved in published (auto-generated, of course) .md files. These aren't identical to the HTML files (which contain tables; markdown version probably(?) wouldn't).

Just a fun idea!

Apparently fs-promise is deprecated.

Blog dev is great but most of my programming stuff I'd like to write about isn't actually focused on the blog. A more general category would be nice!

Right now it depends on the site (output) folder to preexist. This is so bad it could be considered a bug.

Right now they're just embedded in the page, which leads to really bad compiled HTML code. One way that comes to mind is to add an ID to <pre> elements in the markdown code, e.g:

<pre class='math' id='multiply-simple-fractions'>
  \frac{1}{2} \times \frac{4}{3} = \frac{1 \times 4}{2 \times 3} = \frac{4}{6}
</pre>

..But that wouldn't lead to very good source markdown for inline code:

<!-- Now.. -->
Hopefully you already know how to multiply two normal numbers - for example,
you should already know that <code class='math'>3 \times 7 = 21</code>,
<code class='math'>2 \times 4 = 8</code>, and so on.

<!-- After.. -->
Hopefully you already know how to multiply two normal numbers - for example,
you should already know that
<code class='math' id='3x7'>3 \times 7 = 21</code>,
<code class='math' id='2x4'>2 \times 4 = 8</code>, and so on.

I guess it's not as bad as I thought it would be, though. Hmm..

Math currently renders a lot larger than actual text content:

This seems redundant. (In "about" page, under FAQ.)