Code Diary

Welcome to the possibilities of CodePen!

2021-07-14T08:22:33+00:00

So “codepen” looks like it might be a wonderful tool. Let’s check our hyperlink syntax. first link to codepen

second link to codepen

Okay, let’s note a resource:

inline link to resource

and let’s quote: I’m an inline-style link

I’m an inline-style link with title

I’m a reference-style link

I’m a relative reference to a repository file

You can use numbers for reference-style link definitions

Or leave it empty and use the link text itself.

URLs and URLs in angle brackets will automatically get turned into links. http://www.example.com or http://www.example.com and sometimes example.com (but not on Github, for example).

Some text to show that the reference links can follow later.

Welcome to the limitations of a blog with Jekyll!

2021-07-12T08:22:33+00:00

The original for this post was found in the _posts directory. Attempts to use Jekyll as a blogging platform have proven very inconvenient. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.

Jekyll requires blog post files to be named according to the following format:

YEAR-MONTH-DAY-title.MARKUP

Where YEAR is a four-digit number, MONTH and DAY are both two-digit numbers, and MARKUP is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works.

Jekyll also offers powerful support for code snippets:

def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Tom')
#=> prints 'Hi, Tom' to STDOUT.

Check out the Jekyll docs for more info on how to get the most out of Jekyll. File all bugs/feature requests at Jekyll’s GitHub repo. If you have questions, you can ask them on Jekyll Talk.

Getting A Long Streak on FreeCodeCamp

2021-07-11T16:00:33+00:00

It is amazing that the first entry in this blog appeared in April, more than two months ago, and I still do not have a major streak on FreeCodeCamp.

The blog format is not terribly convenient. But it will have to serve. If I really had to do a daily update blog, I would have to find a better format, but the fact is that I am using these daily blog updates as a way to kickstart my work process.

Currently I seem to have a two-day streak that ended. However, today is Monday. Thus it would be entirely reasonable to do something on FreeCodeCamp each day from now until Friday. The projects are a completely unknown quantity, but that makes the effort into an adventure.

It is time to think about using GIT properly

2021-07-02T05:26:33+00:00

Let me see how things work out if I just dump some HTML in this: <!DOCTYPE html>

w3schools.com wikipedia.org

Note: The :hover selector style links on mouse-over.

the

It is time to think about theoretical Computer Science

2021-07-02T00:00:00+00:00

I have somehow committed the wrong file.

It is time to think about CSS

2021-05-16T00:00:00+00:00

I wonder whether I can get this to show up properly even if it does not have a properly placed date in the format:

date: 2021-07-02 13:26:33 +0800

Furthermore I wonder whether I could get an element to show up that had a date in the md filename but not in the text of the md file.

It is time to think about JavaScript

2021-04-26T05:26:33+00:00

So … I have told myself that I would strive for JavaScript certification. This implies that at some point, I must start learning and practicing JavaScript.

By 1357, I was 25% of the way through the freeCodeCamp starting tutorial. I suspect it might be a bit too easy for me.

By 1427, I had finished the first module of Basic HTML and HTML5.

Passed Say Hello to HTML Elements
Passed Headline with the h2 Element
Passed Inform with the Paragraph Element
Passed Fill in the Blank with Placeholder Text
Passed Uncomment HTML
Passed Comment out HTML
Passed Delete HTML Elements
Passed Introduction to HTML5 Elements
Passed Add Images to Your Website
Passed Link to External Pages with Anchor Elements
Passed Link to Internal Sections of a Page with Anchor Elements
Passed Nest an Anchor Element within a Paragraph
Passed Make Dead Links Using the Hash Symbol

Passed Turn an Image into a Link
Passed Create a Bulleted Unordered List
Passed Create an Ordered List
Passed Create a Text Field
Passed Add Placeholder Text to a Text Field
Passed Create a Form Element
Passed Add a Submit Button to a Form
Passed Use HTML5 to Require a Field
Passed Create a Set of Radio Buttons
Passed Create a Set of Checkboxes
Passed Use the value attribute with Radio Buttons and Checkboxes
Passed Check Radio Buttons and Checkboxes by Default
Passed Nest Many Elements within a Single div Element
Passed Declare the Doctype of an HTML Document
Passed Define the Head and Body of an HTML Document

A Fancy Chronology

2021-04-23T08:26:33+00:00

So today is the 23rd of April, 2021, and my only “coding” is really just IT grunt work. I want Jekyll and Github pages to play nicely together.

Welcome to Jekyll!

2021-04-23T08:22:33+00:00

You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.

Jekyll requires blog post files to be named according to the following format:

YEAR-MONTH-DAY-title.MARKUP

Jekyll also offers powerful support for code snippets:

def print_hi(name)
  puts "Hi, #{name}"
end
print_hi('Tom')
#=> prints 'Hi, Tom' to STDOUT.

Check out the Jekyll docs for more info on how to get the most out of Jekyll. File all bugs/feature requests at Jekyll’s GitHub repo. If you have questions, you can ask them on Jekyll Talk.