diff --git a/assets/main.css b/assets/main.css index 3e6357c..b2c81e4 100644 --- a/assets/main.css +++ b/assets/main.css @@ -303,20 +303,14 @@ aside { } .code-highlight { - overflow: auto; - background-color: var(--code-bg); - color: var(--nm); - border-radius: 10px; - padding: 20px 20px 20px 10px; + } code { - border-radius: 10px; font-family: 'Fira Code', monospace; - color: var(--code-fg); - background-color: var(--code-bg); - width: 100%; - margin-left: 16px; + color: var(--vi); + padding: 2px 6px; + /* background-color: var); */ } pre { @@ -327,6 +321,12 @@ pre { pre code { counter-increment: line; + width: 100%; + overflow: auto; + background-color: var(--code-bg); + color: var(--nm); + border-radius: 10px; + padding: 20px 20px 20px 10px; } pre code::before { diff --git a/assets/template.html b/assets/template.html index 24f1535..2d92bb3 100644 --- a/assets/template.html +++ b/assets/template.html @@ -49,4 +49,4 @@

{{title}}

- \ No newline at end of file + diff --git a/index.html b/index.html index 92b4fe8..62fa9af 100644 --- a/index.html +++ b/index.html @@ -12,21 +12,23 @@ - +
@@ -39,7 +41,8 @@ |____/ \___|_| | .__/ \__, /___/___\__,_| |_| |___/ "> - +

👋 Hello, i'm derpyzza

I'm a programmer and an artist. I like experimenting with low level technologies, @@ -60,23 +63,28 @@

  • games
    • +
  • + the 'why make another x' list +

    • -

    Also, here's a complimentary weird fish thing, on the house. It's not a very interesting fish thing, nor a very unique one. However, how many other websites have you come across with this specific fish - on the first page? +

    Also, here's a complimentary weird fish thing, on the house. It's not a very interesting fish thing, nor a very + unique one. However, how many other websites have you come across with this specific fish + on the first page?

    checkmate.

    - An image of a little pixel art fish-like creature standing atop a chiseled-stone looking platform. The platform has the fish standing on one edge, and a couple bits of seaweed growing on the other. You gaze upon this image and feel a sense of serenity wash over you. It feels good. + An image of a little pixel art fish-like creature standing atop a chiseled-stone looking platform. The platform has the fish standing on one edge, and a couple bits of seaweed growing on the other. You gaze upon this image and feel a sense of serenity wash over you. It feels good.
    - + \ No newline at end of file diff --git a/jenny.py b/jenny.py index dc9a221..f53c04a 100755 --- a/jenny.py +++ b/jenny.py @@ -55,6 +55,7 @@ def preprocess_file(file): 'generate_toc': True, 'post_languages': ['en'], 'file_name': file.name, + 'ignore_index': False, } keep_scanning = True for line in file: @@ -67,15 +68,19 @@ def preprocess_file(file): # If only one item in list just convert it into a string if len(args) == 1: args = "".join(args) - - if command == 'generate_toc': - if args[0].strip().lower() == 'false': - vars['generate_toc'] = False; - # default case + + if args.lower().strip() == 'false': + print("FAAKLSE") + vars[command] = False + elif args.lower().strip() == 'true': + print("TRUEEE") + vars[command] = True else: - vars['generate_toc'] = True + vars[command] = args else: vars[command] = args + print(f"vars: {vars}, cmd: {command}, args: {args}") + elif stripped.startswith("---"): keep_scanning = False continue @@ -303,7 +308,10 @@ def format_file(post, template): try: template = template.replace("{{title}}", post['post_title']) template = template.replace("{{content}}", post['post_content']) - template = template.replace("{{date}}", pretty_date(post['post_date'])) + if 'post_date' in post: + template = template.replace("{{date}}", pretty_date(post['post_date'])) + else: + template = template.replace("{{date}}", " ") except Exception as err: print(f"Error: could not process file {post["file_name"]}, err: {err}") exit() @@ -333,7 +341,7 @@ def process_posts(): (has_links, has_notes, links, post['post_content']) = process_notes(post['post_content']) post['post_content'] = process_headings(post['post_content'], post['generate_toc']) post['post_content'] = build_footnotes(post['post_content'], links, has_links, has_notes) - post['post_content'] = process_code_blocks(post['post_content']) + # post['post_content'] = process_code_blocks(post['post_content']) file_name = os.path.basename( f ) destination = os.path.join( out_dir , os.path.splitext( file_name )[ 0 ][7:] + ".html" ) @@ -361,6 +369,8 @@ def process_index(file: str): file_name = f"{out_dir}/{file}.html" for post in reversed(posts): + if post['ignore_index']: + continue year = "".join(post['post_date']).split('.')[0] if not (year == last_year): # Nasty little hack, but i have a slight headache and i'm losing diff --git a/public/about-jenny.html b/public/about-jenny.html index bd46494..d22dd0f 100644 --- a/public/about-jenny.html +++ b/public/about-jenny.html @@ -52,7 +52,7 @@

    # Why

    # How

    does it really work? ( as of the time of writing ) jenny is essentially just a small python script that expects three things: a src/ directory that contains .md files, an assets/ directory that contains a stylesheet and two template .html files ( one for the main page, and one for the actual posts themselves ) and a public directory. the script reads through every .md file in the src/ directory, and first off preprocesses the file for some metadata. metadata for jenny follows the following syntax: -

    $command args...

    +$command args... metadata must always begin with a dollar symbol, immediately followed by a command or keyword that tells the program what kind of data it is, followed by a space delimited string of arguements to the command. currently, jenny only supports three commands: title, subtitle, and data. all three of these are used in displaying the title of the post on the post page, as well as displaying the title on the main page. after the preprocessing stage, jenny converts the raw markdown posts to a .html page using the aforementioned template files, and stores the post to a list of posts along with their titles, subtitles, and dates. jenny then just takes all that data, and feeds it through another template to produce an index file as the landing page of the blog. and... that's it! jenny is in itself a super basic script. it only does what it needs to, and nothing else. it ends up being slightly not user friendly as a direct cause of that simplicity sometimes, but that's my fault for just rushing the implementation a bit hehe.

    @@ -82,4 +82,4 @@

    # Final notes

    - \ No newline at end of file + diff --git a/public/hacky-script-perfect-script.html b/public/hacky-script-perfect-script.html index 5bd05ae..beee392 100644 --- a/public/hacky-script-perfect-script.html +++ b/public/hacky-script-perfect-script.html @@ -73,4 +73,4 @@

    # - \ No newline at end of file + diff --git a/public/on-writing.html b/public/on-writing.html index 65205d3..290ebcd 100644 --- a/public/on-writing.html +++ b/public/on-writing.html @@ -69,4 +69,4 @@

    random rambling on writing, or something

    - \ No newline at end of file + diff --git a/public/star-wars-visions-season-2.html b/public/star-wars-visions-season-2.html index 80263e0..bca865c 100644 --- a/public/star-wars-visions-season-2.html +++ b/public/star-wars-visions-season-2.html @@ -91,4 +91,4 @@

    # The Pit [ 1/10 ]

    - \ No newline at end of file + diff --git a/public/why-bother.html b/public/why-bother.html new file mode 100644 index 0000000..25a2c7f --- /dev/null +++ b/public/why-bother.html @@ -0,0 +1,103 @@ + + + + + + + + + Derpyzza's site + + + + + + + +
    +
    +
    +
    + + Go back +
    +

    the 'why make another $THING' list

    + +
    + +
    +

    often times when working on a hobby project where you're attempting to (re-)create a custom version of something that already exists, you'll come across questions from other people that are always something along the lines of "$THING already exists, why are you making another one?". +i have prepared a handy dandy list of rebuttals that can be used to counter their misplaced concerns. +simply tick all that apply and send it over to them ( Or stick it somewhere on your project's documentation or website if it has those ).

    +

    the list will be updated as i come up with more rebuttals.

    +

    here's the list:

    +

    # I'm making $THING because:

    +
      +
    • [ ] it's fun
      • +
    • [ ] i felt like it
      • +
    • [ ] i bet i can sell this and get rich
      • +
    • [ ] making $THING will help me stroke my ego
      • +
    • [ ] it'll probably look real nice on my resumé
      • +
    • [ ] people will think i'm a cool person for having made my own $THING
      • +
    • [ ] i will think i'm a cool person for having made my own $THING
      • +
    • [ ] there arent enough versions of $THING out there already and there needs to be more!
      • +
    • [ ] it's trendy right now and i want to hop on the hype train myself
      • +
    • [ ] i'm bored out of my mind and if i don't distract myself with this i'm going to lose my mind
      • +
    • [ ] i happen to have the free will required to engage in this activity
      • +
    • [ ] it's a good educational experience
      • +
    • [ ] it fills some gap that i found in my knowledge/experience
      • +
    • [ ] the other version(s) of $THING sucks because it's:
        +
      • [ ] boring
        • +
      • [ ] poorly made
        • +
      • [ ] UNWORTHY!!!
        • +
      • [ ] bloated
        • +
      • [ ] messy
        • +
      • [ ] hard to use
        • +
      • [ ] difficult to understand
        • +
      • [ ] poorly documented
        • +
      • [ ] expensive
        • +
      • [ ] hard to acquire
        • +
      • [ ] slow to use
        • +
      • [ ] tedious to use
        • +
      • [ ] doesn't work very well
        • +
      • [ ] proprietary and i can't modify it
        • +
      • [ ] open and i can modify it, and i take issue with that for some reason D:<
        • +
      +
      • +
    • [ ] the other version(s) of $THING is fine but:
        +
      • [ ] i wish it did x better
        • +
      • [ ] it's missing some features that could really enhance it / my usage of it
        • +
      • [ ] difficult to aquire
        • +
      • [ ] unnecessarily bloated
        • +
      • [ ] poorly documented
        • +
      • [ ] expensive
        • +
      • [ ] tedious to use
        • +
      • [ ] doesn't fit enough of my use-cases for it to really be good for me
        • +
      • [ ] fails to offer x functionality
        • +
      • [ ] it's proprietary and i can't modify it
        • +
      +
      • +
    +
    + +
    + +
    + + + + + diff --git a/public/writing-systems-evolved-from-material-limitations.html b/public/writing-systems-evolved-from-material-limitations.html index 9e7af0f..80f90b1 100644 --- a/public/writing-systems-evolved-from-material-limitations.html +++ b/public/writing-systems-evolved-from-material-limitations.html @@ -53,4 +53,4 @@

    Writing systems evolved from material limitations

    - \ No newline at end of file + diff --git a/src/241106-why-bother.md b/src/241106-why-bother.md new file mode 100644 index 0000000..0155f72 --- /dev/null +++ b/src/241106-why-bother.md @@ -0,0 +1,55 @@ +@post_title the 'why make another x' list +@ignore_index true +@generate_toc false +--- + +often times when working on a hobby project where you're attempting to (re-)create a custom version of something that already exists, you'll come across questions from other people that are always something along the lines of "`$THING` already exists, why are you making another one?". +i have prepared a handy dandy list of rebuttals that can be used to counter their misplaced concerns. +simply tick all that apply and send it over to them ( Or stick it somewhere on your project's documentation or website if it has those ). + +the list will be updated as i come up with more rebuttals. + +here's the list: + +# I'm making $THING because: + +- [ ] it's fun +- [ ] i felt like it +- [ ] i bet i can sell this and get rich +- [ ] making `$THING` will help me stroke my ego +- [ ] it'll probably look real nice on my resumé +- [ ] people will think i'm a cool person for having made my own `$THING` +- [ ] *i* will think i'm a cool person for having made my own `$THING` +- [ ] there arent *enough* versions of $THING out there already and there needs to be more! +- [ ] it's trendy right now and i want to hop on the hype train myself +- [ ] i'm bored out of my mind and if i don't distract myself with this i'm going to lose my mind +- [ ] i happen to have the free will required to engage in this activity +- [ ] it's a good educational experience +- [ ] it fills some gap that i found in my knowledge/experience +- [ ] the other version(s) of `$THING` sucks because it's: + - [ ] boring + - [ ] poorly made + - [ ] UNWORTHY!!! + - [ ] bloated + - [ ] messy + - [ ] hard to use + - [ ] difficult to understand + - [ ] poorly documented + - [ ] expensive + - [ ] hard to acquire + - [ ] slow to use + - [ ] tedious to use + - [ ] doesn't work very well + - [ ] proprietary and i can't modify it + - [ ] open and i *can* modify it, and i take issue with that for some reason D:< +- [ ] the other version(s) of `$THING` is fine but: + - [ ] i wish it did x better + - [ ] it's missing some features that could really enhance it / my usage of it + - [ ] difficult to aquire + - [ ] unnecessarily bloated + - [ ] poorly documented + - [ ] expensive + - [ ] tedious to use + - [ ] doesn't fit enough of my use-cases for it to really be good for me + - [ ] fails to offer x functionality + - [ ] it's proprietary and i can't modify it