The WordPress themes from 2010 – 2017. Copies of the screenshot.png file in the theme folder.
Today I’ve experiemented with the Open Graph Protocol. Why not write a plugin that will add the protocol to any WordPress page. Here’s my first draft.
So the new verson of WordPress has arrived. With it came a new theme: Twenty Seventeen. It’s an attempt to combine the (perhaps too) popular “one-pager” with WordPress content-managing.
The theme has many interesting features. One important addition is the .svg icon theme. These days the SVG format becomes more and more important. Twenty Seventeen may be a proof of concept here.
Of course I had to try the theme. The design style is “big image” or even “big video” if you dare to use that option.
The theme has improved greatly since the beginning in october 2016. The process began on Github. Here a team from Automattic co-worked with the WordPress open source community. 68 participants or more gave input and suggested code.
When the theme was ready for the core it moved to Slack. In the end it was integrated in the wordpress-core code.
A web page is dedicated to the development process. Here you can see the mock-ups and follow the general development of the new core theme for WordPress.
The image below is one of the “hi-fi mock-ups” that was used during the development of Twenty Seventeen.
In this post Helen Hou-Sandi suggests working on starter content to the new Twenty Seventeen theme. UX should be a major concern in all themes:
“While theme review guidelines need to be finalized and documented, it is anticipated that themes being submitted to WordPress.org will be expected to select from core-provided content to promote consistency and to help keep the theme review process from becoming lengthier, with exceptions being made on a case by case basis. Themes being distributed outside of WordPress.org are not subject to the same review process; however, it is recommended that consistent user experiences be the primary consideration in how starter content is chosen and implemented.” (HHS op.cit.)
Right now my research and programming go hand in hand. Saving all sources and notes in a database proved to be a very good idea. Adding new sources to the database is easy in Adminer.
Whenever new additions are made to the database, it’s a matter of seconds to compile a new bibliography file via my Python script.
Now I write, and write. Texts, notes, ideas, chapters, structures … poor out. The database is a major tool in the creative work. Quotations are made via the ID in the database. Since the value is unique there are no conflicts in the bibtex file.
In the actual texts its a matter of adding @wp_81 – or whatever the id of the relevant source may be.
All my texts are written in markdown. I can compile the texts to .pdf, .epub, .docx etc. via a Pandoc script i bash.
With this “toolbox” it’s easy to write the academic dissertation.
Right now the writing process is in a phase of “write-out”. I don’t care to finish anything. It’s like drawing a sketch on paper. But when the chapters are compiled – it turns into a report, with all the academic features: lists of content, notes, and a very precise academic bibliography.
I never thought, that writing and programming were related in this way. But it’s a fact: programming and (academic) creative writing are related.