wordpress / book Goto Github PK

Greetings!
Can I be of help by translating this book into the Filipino language?
Thank you.

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.

The chapter on WordPress themes requires some statistics on WordPress' growth.

How do you want Haiku's submitted? As pull requests!? That'd be a first for me. What a great project, looking forward to the final product for sure.

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?

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.

Chapter 2 has quite a strong sense of place for Corsica. Add a few sentences about Houston and Stockport to create depth and texture.

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.

Generally speaking, books use the em-dash, while regular text replaces it with two en-dashes. The book here seems to use two en-dashes. Can we switch it to using em-dashes instead?

Not sure if you are interested, but I've been using WordPress since 0.7 and have been part of the community. I took over Blogging Pro after it was sold, and watched as it was removed from the WordPress Planet feed. I worked with Charles Stricklin on the WordPress podcast, and with Jeff Chandler on the WordPress Weekly podcast. I've done a little bit of everything with regards to WordPress. I am not sure any of it is worthy of the book you are trying to create, but I'd like to thin I was part of the history/community of WordPress... at least at some point.

When accessing this page: https://milestonesbook.wordpress.com/2015/11/13/part-one/ in the online version, I encounter a broken image. I'm using the latest build of Chrome on a MacBook Pro. https://cloudup.com/cUbiDa71NCL

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.

(Regarding e8c5d23#diff-1da584e79e0bf44413b66c9fe8992efeR225, as noted in this comment)

Once the application to register the trademark was submitted, Automattic had to go about protecting the trademark. This meant getting people who used WordPress in their domain name or product name to change it. It wasn't entirely straightforward. WordPress had been a community project for two years and many people felt that they had a stake in it.

It might be worth mentioning that the registration of the trademark and its new implications for community sites never were communicated openly to the community on the wordpress.org blog[1]. WordPress had been a community project not only “many people felt that they had a stake in it”, but international communities had been starting to group around[2], some of them already running with a strong user base.

Instead of providing detailed information for those international communities through channels they were used reacting to (such as the dot org blog where new release got announced) —information on what they could and could not do with their “wordpress dot something” domains and why— Automattic chose their next action after putting up the Codex page in sending out directives.

At least for one international community —Germany, up to that day the largest of non-anglophone communities— this had major consequences. Key community members felt like they who had helped building WordPress’ international success suddenly had been degraded to community members “of a second class”. Or to put it bluntly: people were plain pissed[3].

Unfortunately, yet maybe comprehensibly from a human perspective, those community members did not pick up the conversation themselves, but chose to turn their backs on Automattic and the “crowd over there” (America) which resulted in a long-lasting breakup of the relationship between Automattic and the dot org project on the one and a growing, but unresponsive German community on the other side —a breakup that has started to heal only lately since a new generation of germanophone community workers has started to get involved in the dot org context again.

[1] The dot org blog goes way back to April 2003. None of the posts from 2005, 2006 (year of filing trademark registration), 2007 (year of actual registration) or 2008 contain the word “trademark”. The earliest mentioning of WordPress being a trademark on the dot org blog is from Sep 9, 2010, titled WordPress Trademark Changes Hands—over 3.5 years after the registration had been completed.
[2] WordPress Deutschland says hello on Nov 1st, 2004. In order to respect the new domain policy, wordpress.de was handed over to Automattic later on. It now redirects to the germanophone edition of wordpress.com.
[3] It’s hard to find written evidence of that condition, apparently none of the respective interactions did make it into public channels. Obviously no one on either side —Automattic and WordPress Deutschland— had intentions to start a public discussion on the issues at hand. A glimpse of critique can be found in statements like this or this or comments like under this post. Also the relationship between the two obviously had experienced damages already during the Link Lift issue in 2004, so the trademark issues might only have added to an already existing disharmony —which after all will remain speculation, though, as none of the individuals involved back then seems to show any interest publicly talking about those things.

The method used for linking in Chapter 3 isn't the same as the one used for Chapters 1 and 2. Is there a specific reason for this? I would imagine consistency would be more desirable?

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! 😃

On part 37, a quote from Brad Williams is opened but never closed. Relevant portion below

Brad Williams (williamsba1) recalls now: “I think it probably would have been more beneficial across the board for some more open conversations between the Foundation and the organizers to make sure, one, that these guidelines make sense and that we're all on the same page and if there was any concerns get those out in the open. As with other decisions in the past, the guidelines weren't part of a conversation between the Foundation and the WordCamp community. When they appeared, they seemed unilateral and the reasons behind them were poorly communicated.

I'd implement the fix myself but I'm not 100% certain where his quotation actually ends.

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.

Hello, I am very interested to read this book. May I translate this book into Indonesian? I am also an Indonesian translator. Thank you.

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.

I've recently done an interview with Francois Planque of b2evolution. Look at integrating a few quotes or information from that interview in Chapter 3.

"Theme sellers that seel their themes with a 100% GPL license are supported by WordPress." should be sell

"If a speaker, volunteer, or organizer is distributing a WordPress product it needs to be 100& GPL, I.e. The CSS, JavaScript, and other assets need to be GPL, just like the PHP." Replace the & symbol with a percentage sign. 100% GPL

"In early 2013, Theme Forest, the theme marketplace run by Envato" ThemeForest should be one word.

"It offers exposure and access to a huge community of users. With the theme shop marketplace becoming increasing saturated it became more and more difficult for new theme sellers to break through." Should be increasingly saturated

See https://wordpress.org/news/2008/11/the-results-of-project-icon/
It's not mentioned in the book anywhere, but it had a big impact on the new layout of the admin, and may have been the first crowd-sourced design feature by an open source project in history.

I tried to download it a bunch of times. It finishes, but I receive this error:

http://screencast.com/t/4YjqX5iAE

I've added a discussion in Chapter 2 about the flaws with b2's code and the discussion on the internet about how poor it was (from a pro dev perspective). It's interesting that seasoned developers complained about the code but its simplicity meant that people learning PHP (Matt, Ryan, Alex, etc etc) found it easy to work with. Experienced developers hated it, new developers loved it.

To avoid overlap, this paragraph now feels more relevant in Chapter 2:

It wasn't all bad, however. Michel's inexperience also meant that the code had a level of simplicity that made it easy for other developers to understand. Whereas a more experienced developer might write complex code, Michel often took the simplest route to solve a problem. "In a way it was beautiful because it was so simple," says developer Alex King, alexkingorg, "It wasn't elegant but it was very straightforward and very accessible. For someone who didn't have a lot of development experience coming in --- like me --- it was very comfortable understanding what was going on."

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.

Update theme chapter with information about solostream - https://web.archive.org/web/20071011063942/http://www.solostream.com/2007/06/09/wordpress-blog-theme-bosco-20-widgets/

Published earlier than Revolution.

I would love to have (and help create) an epub version of the book.
Since epub internally uses html it is pretty easy to create. I like to use http://calibre-ebook.com/ for all my ebook stuff and the editor is pretty nice to create epub books.
It should be pretty easy to create an automated process to convert markdown into html and pack it into an epub file.

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.

In chapter 2, you say PHP is a recursive acronym for PHP: Hypertext Processor, but actually it's PHP: Hypertext Preprocessor.
See PHP's intro.

Instead of an instruction on how to press "Raw" it might be more convenient to have a tagged release and attach files as binaries.

Line 68:

At the time, Dougal wasn't a b2 user, though he had investigated using b2 for his blog. In November 2002, he posted [about writing his own blogging software][44], which he called dBlog. Dougal wanted a number of key features in in his blogging software, including security, connectivity to other blogging platforms, and content separated from presentation Finally, Dougal wanted configurability --- dBlog would have a rich API enabling developers to extend it.

This sits better within chapter 2. Move to chapter 2, remove this section from chapter 3 and revise section for consistency.

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.

Chapter 2 finishes with the abandonment of b2. Look at the opening of Chapter 3 and look into whether it should be revised to open with the section on forking. Also, we could move the section on b2 evolution to the opening.