I'm trying out a new logic for the home page. Instead of using infinite scroll to eventually show all posts, we're showing only the posts for the current and previous month, just like Scripting News. We don't link to anything older, since old news is no longer news, and good older posts will have links from elsewhere. 

There will be an option to show the traditional  WordPress pagination links to older posts for those who prefer that behavior.

It's nice to have the baseline around, because now I have something to match the presentation of H3's with. The next version of WordLand will have that worked out.

Had to back out of the Styles panel of the Settings command, I did it way too fast, each feature it added had to be tested in this very particular context.

The context is Medium Editor, Markdown and WordPress. None of which were designed to work with each other. We're lucky to have a core subset that works, enough to support writers.

I think to get a really complete editor, you have to start with Markdown or HTML and work it out with WordPress.

I have made the style of H3 agree with the style of in the Baseline theme.

My answers to the questions from May 4, 2025:

1. As I understand it, with a Business plan on wordpress.com you can install any third-party theme. 
2. Looking at the WordLand timeline, every post has a headline of author name and date, whether there is a title or not. That looks more balanced that simply having no headline for titleless posts.
3. I think that whether WordLand can add CSS to a site or a post depends on the WordPress.com REST API. At first glance I don't see anything about styles. On a self-hosted site it would be possible to extend the API to accept CSS (ChatGPT), but would WordLand to access that over wordpress.com?
4. OK
5. OK, we can try that
6. OK

Other problems I've noticed

1. Block quotes are not styled properly (they are indented, but no line to the left).
2. On the home page for untitled posts, there is no link to the story page for the post.
3. Bold italics were not working, but do now (fonts issue).
4. Inline code markup like this  isn't very distinguishable from normal text (issue on GitHub).

This is a list of things that I want to try out on the new baseline theme.

Here are five great MLB first basemen and what made each of them especially interesting:

1. Lou Gehrig – The "Iron Horse" of the Yankees, famous for his durability, humility, and tragic early retirement due to ALS, which now bears his name.

2. Albert Pujols – A modern legend known for his all-around hitting, consistency, and longevity, finishing with over 700 home runs.

3. Willie McCovey – Towering lefty slugger for the Giants, feared for his monstrous power and iconic presence in the batter’s box.

4. Keith Hernandez – Brilliant defensively, redefining how first base was played with range, quickness, and leadership—also a memorable personality.

5. Frank Thomas – “The Big Hurt” dominated the ‘90s with his intimidating size and incredible hitting eye, combining power with patience.

Thanks for listening, this has been a test!

I've applied the single column layout proposed by Christy Nyiri. I personally think it looks fantastic. 

Here are some WordLand styles.

Heading 1

Heading 2

Heading 3

This is a block quote. (This doesn't seem to be styled yet.)

Bold, italics, underlined (hmm, it's not underlined). 

An ordered shopping list:

1. Bread
2. Milk
3. Eggs

Notes as an unordered list:

•  The next/previous links have returned to the WordPress default instead of large arrows only. Update: That was my bug, now fixed.
• As Christy noted, the child elements of the Post Template block are a little weird at inheriting global padding, as evidenced on mobile.
• Are H1 and H2 way too big? Update I've bumped down the font-sizes of H1 to H3 to large, medium, and normal. H1 now matches the size of the post title, and H3 matches the size of normal paragraph text.

Here's a paragraph that appears under the unordered list.

Scott, a discussion on the support repo about whether we should have H4 in the popup menu led me to consider an option I had been thinking about in the background — letting the user configure the contents of that menu. It's basically a list of names, chosen from these:

bold, italic, underline, anchor, h1, h2, h3, quote, unorderedlist, orderedlist, pre, removeFormat, justifyLeft, justifyCenter, justifyRight, justifyFull, indent, outdent

They all seem to work. Special provisions need to be made in the baseline site for h1, h2, and h3, esp h3.

h3 should be the same font-size and line-height as a paragraph, but boldface. 

It's the best way to add a headline to writing in wordland. Imho any other size starts getting into MySpace territory.

For Change #5, I once again used an add_filter function to replace the HTML generated by WordPress, this time for the next/prev links. The links show only an arrow at 1.5em (24 px), no underline, with the post title in the title attribute of the anchor tag so it shows up as a tool tip.

For Change #10, since we can include PHP code in the theme, we don't need to use JavaScript to filter out the Uncategorized category. We can use an add_filter function on the get_the_terms hook in functions.php to remove Uncategorized before the wp:post-terms block displays the categories.

The block also has a parameter for the prefix to the displayed list, so we changed it from "Posted in " to "Categories: ".

I thought Change #11 would be simple. The icons are in a social-links block, and an RSS feed is among the supported services.

However, adding

<!-- wp:social-link {"url":"#","service":"rss"} /--> 

to the sidebar failed. I had to dig into the WordPress code itself to find the service is named "feed", not "rss". The correct syntax for the RSS feed icon is

<!-- wp:social-link {"url":"#","service":"feed"} /-->.

🙄

Hooking up the correct link to the icon is a task for later.

Update: We put an add_filter function in functions.php to put the actual feed link on the icon (Commit 38b1a45).

For Change #4 some adjustments to the post body text were requested.

• Font size should be 18px
• Font weight should be 400
• Font color black on white background
• Values should be able to be changed in browser dev tools

In block style WordPress themes most of the CSS is in the theme.json file.

• The font size in a post is set in core WordPress to the CSS variable –wp–preset–font-size–normal. "normal" is set in WordPress itself to 16px, so I set "normal" in theme.json to 18px.
• I also increased the "small" font size from 16px to 18px. 
• Under "typography" I changed the font weight from 300 to 400.
• Also under "typography" the background was already set to white, so I left it.
• Yesterday I posted on how to view and change CSS variables in dev tools.  
• On my own, I also increased the size of "x-small" text from 14px to 16px, since the text in the sidebar and the footer seemed too small compared to the 18px post body text.

Once these changes are tested, they will become version 0.0.2 of the theme.