Finished epub version on my book reader and had bit of an issue with link anchors — they often covered whole area of screen where I tap to scroll. Paragraphs worth of a single link or consecutive links.

There are several ISO639 levels. As lvl 3 is broken (inconsistent), lvl 5 is unfinished and lvl 1 only contains country codes, I'd recommend to change the README to use lvl 2. The ISO 639-2 uses language_COUNTRY codes and therefore fits for differences like German in Austria, Switzerland, Germany, etc. as well.

I'd like to propose that the book would be better served to reference paid themes as "commercial" versus "premium" wherever possible and still keep context.

I know that some chapters, like chapter 29, refers to the "premium" theme marketing element, but within that chapter where it's not discussing the "premium" moniker itself, but labeling a theme shop, and in other chapters where it's simply labeling a theme shop as premium, the book would be better to showcase the themes as commercial instead.

A couple of quick examples:

Chapter 29:

For designers and developers making free and premium themes, what distinguished them was the time and effort they put into them, and the level of effort required to set them up. In an interview in June 2008, premium theme developer Darren Hoyt talks about the differences between creating a free and a premium theme. He outlines his considerations:

The second instance I think, at least, should say commercial, as it's descriptive of the real thing, not the practice of calling themes premium. The third makes sense as premium. The first is debatable...

Chapter 31:

Premium theme developers and the wider community were annoyed.

and

As the first to embrace the GPL, Brian Gardner advised other premium theme sellers.

Both of these instances would be better served to say commercial, I believe. The middle of the chapter that explains Matt's stance on "Premium", "Proprietary", and other labels is more difficult to determine appropriate labeling.

In general, I'd love to see the book notate commercial instead of premium when describing themes that cost money. Of course, this requires balance with the common terminology that was used during that period and now, where appropriate.

I completely trust Siobhan's ability to make that balance, but would at least like to review the usage of the word "premium" throughout the book to see if it can or should be replaced with more accurate terminology.

Hi! Trying to avoid spoiling too much of the book, but couldn't resist reading a few select chapters. :)

In Part 3/24-habari.md, it contains the following:

Notable BDFLs are Linus Torvalds of Linux and Rasmus Lerdorf of PHP.

However, Rasmus doesn't actually hold the title of BDFL, as PHP's decision-making process is consensus based. A much better example would be Guido van Rossum of Python, for whom the term was originally created (citation).

Note that the above Wikipedia article does claim that Rasmus is the BDFL, although it sites a secondary source with no verification for the claim. Van Rossum's claim has many more documents to support it, including an article written by him talking about the history of the title, and an entry in the Jargon File.

I'm not sure whether you think it's necessary or not, but where you're explaining what a permalink and trackback are, you use the term ping (also jargon in this context) without explanation.

I would think if someone didn't know what a permalink or trackback was, they also won't understand what a ping is.

• Fix Community -> To Contact subheading not displaying correctly.
• Change italic subheadings to proper headings for semantics, automatic page anchors and to make it easier to scan.

The image -- https://github.com/WordPress/book/blob/master/Resources/images/44/post-formats.jpg -- may be better off cropped just a few pixels shorter. The side meta box currently just shows a line at the bottom of the image where the next meta box would stop, and it feels a bit awkward.

I don't think GPLv2 is compatible with Creative Commons Sharealike license.

As far as I know the only CC license that is GPL compatible is CC0

From Gnu GPL:

Creative Commons Attribution-Sharealike 2.0 license This is a copyleft free license that is good for artistic and entertainment works, and educational works. Please don't use it for software or documentation, since it is incompatible with the GNU GPL and with the GNU FDL.

My 2¢..license compatibility is pretty confusing considering.. it's a book on github which might be considered software.

I enjoyed reading the first part of the WordPress book and would like to propose the following changes. Let me know what you think and thank you for your work.

I can't find anywhere that lists all of the release leads for each version since WP transitioned to release leads.

https://make.wordpress.org/core/tag/release-lead/

Could they be added to the relevant chapter or an appendix?

Hi! Seeing that the Story of WordPress is still being written, are there any plans to have a sequel or append to the current story? ps: I just read the part about The WordPress Foundation, and found it very insightful! 😃

I tried uploading to Google Play Books and it says "file cannot be processed." then has a "learn more" option taking me to this page: https://support.google.com/googleplay/answer/3097151?visit_id=636829228570910203-3019479125&rd=1

Something about the formatting (I assume) of the ePub isn't allowing it to be added there. Would be nice if it worked.

I'm writing a master's thesis about WordPress, and it is unclear to me how to cite this book. Specifically, what is the author? Was it first released in 2015? Maybe this information could be added to the book itself? Thanks.