Fine template for a widget: https://pippinsplugins.com/simple-wordpress-widget-template/
Author: Per Thykjaer Jensen
-
WP Core
The Slack channels for core developers:
Core meetings this week:
All meetings in the WordPress Slack #core channel unless specified otherwise.
- tirsdag den 13. september 2016 01.00 CEST in #core-restapi
- Multisite Weekly Chat on tirsdag den 13. september 2016 18.00 CEST in #core-multisite
- Editor Weekly Chat onsdag den 14. september 2016 20.00 CEST in #core-editor
- Weekly Dev Chat on onsdag den 14. september 2016 22.00 CEST
- Multisite Bugscrub on torsdag den 15. september 2016 22.00 CEST in #core-multisite
- Themes Weekly Chat on fredag den 16. september 2016 20.00 CEST in #core-themes
- Media/Images Weekly Chat on fredag den 16. september 2016 21.00 CEST in #core-images
I’ll follow the procedings in #core-themes channel.
-
Following WP training
Started browsing through the online lessons. Following the debate and progress in general. Skimmed the loop lesson.
IMHO colored syntax and line numbers is missing. It is hard to read the samples.
Also – from a teacher’s point of view – I’d like to know something about the outer framework. How long is the lesson intended to last? How many students are in the class? Where do the students get hands on experience?
I miss a didactic strategy:
- A time to talk
- A time to work
- A time to give feedback
The loop lecture
You cannot set time aside to “install WordPress” in this lecture. If there is no running WP on all PCs you’ll end up using all the time for database or serverside issues. And get nowhere.
When I read a subsection like “Setting up a default loop” there is a # link. But a # does not say anything about the link. So the reader is lost. Text and code mingle in a way that makes the lesson hard to read. Here is a sample:
It sets up all the template tags, like the_title(),
to display the correct information for each item.
–>
<?php while ( have_posts() ) : the_post() ?><!–
This code will be repeated for each item in the loop.Reading stuff like this is hard. Here I’d prefer a colored syntax. And it would be supercool if it was possible to experiment with different loops on the website.
There is room for improvement in the “Make WP training” Codex.
-
Twentyseventeen
The work on twentyseventeen begins these days. The files are shared on github. And a team of designers are working together. Here are notes from the first meeting:
- Say Hello to Twentyseventeen
The standard themes on WP are called twenty-(someting). So far Helen Hou-Sandi tells, that Twentyseventeen will be a responsive onepager.
- Here is a gallery with features and idea.
The team call out for WP developers:
How can you get involved?
There will be weekly meetings every Friday at 18:00 UTC in #core-themes starting today. During that time, the focus will be on the theme itself. If you are interested in contributing, keep an eye out here for updates or join us in #core-themes in Slack.
If you have some early thoughts on what would make this a great WordPress experience, or if you’re generally interested in participating, sound off in the comments. Please hold any design feedback for Friday’s meeting. where we can have a conversation about it in greater depth.
Here is a mockup from Helen Hou-Sandi’s post showing several devices.
The theme is designed by Mel Choyce.
Twentyseventeen mockup Helen and Mel work at Automattic. So the themes grow i a forest that’s more or less planted by Matt Mullenweg’s company.
The early stage is shared on Github. As soon as the code is considered stable it will become part of the WP core. Here’s the Theme Review Team guidelines.
Issues on Github
If you want to know the developers thoughts and visions go to “Issues“. A good example is the debate on .SVG in place of icon fonts. Follow this thread.
By now there are only 31 issues.
-
Cases
Getting the cases via the central hand in WF is not as easy as presumed. The system is more or less manual. Getting cases or conducting searches is not an option.
Plan B: source = lecturers.
The general research will continue. Here the sources are:
- WP debates: participation.
- Focus I: Core.
- Focus II: Training.
The project description had to change. A stakeholder thought that “there are enough books about WP”. I agree – also because my involvement in WordPress is research as opposed to evangelism.
- WP debates: participation.
-
CMS Usage Denmark
Se denne oversigt: http://trends.builtwith.com/cms/country/Denmark
-
Officiel webtekst klar
Så er den officielle webtekst ved at være klar. Projektbeskrivelsen er på vej ind i den sidste iteration, hvor multimediedesigns input indarbejdes. Det ligner et sceneskift fra projektbeskrivelse til research / literature review.
-
What’s important in code
So your code works as intended.
So far so good, but:
– Do you know why?Per Thykjær Jensen (2016)
-
Projektbeskrivelse IV
Forskningsspørgsmålet skal foldes ud i bulletpoints for “variablerne”. Dokumentet er ved at falde på plads. Primo næste uge skal det sendes til endelig godkendelse på EAAA.
Publikation: dansk eller engelsk? That’s the question. Papir eller e-produktion. Tror mest på e (fremstillet i Latex).
-
Projektbeskrivelse III
Tredje iteration af projektbeskrivelsen skippet med posten. En væsentlig ændring er præcisering af forskningsspørgsmålet til:
Hvilken viden om kode og workflows er nødvendig for at udvikle avancerede WordPress-løsninger til virksomheden?
Det er en meget varm dag. Ventilator kører for fuld hammer. Altandøren er åben. Solen skinner over Aarhus.