Yes, I’ve been away. Crushing deadlines will that to a person.<\/p>\n
Tomorrow, I promise my long-awaited blog post on Star Trek: The Next Generation\/Doctor Who<\/i>: Assimilation2<\/sup><\/i> #4. It’s something I’ve been wrestling with for about two weeks now.<\/p>\n At the moment, though, I’m going to write about where things are with my website redesign.<\/p>\n 1) Mobile<\/b><\/p>\n I thought about trying to figure out how to make the theme I’m using responsive to display width. I spent some time studying CSS code for some other WordPress themes, looking at how others made the 960 Grid<\/a> responsive, that sort of thing.<\/p>\n I decided, instead, to make things easy.<\/p>\n I was pointed in the direction of a WordPress plugin, Device Theme Switcher<\/a>. This plugin enables a site to serve a different theme if someone arrives on a mobile phone or a tablet, and you can specify themes for both eventualities.<\/p>\n For the mobile phone, I’m going to use Minileven<\/a> as the theme. For tablets, I will probably use Twenty Twelve<\/a> once that’s released for self-hosted WordPress.<\/p>\n Both I’ll modify somewhat with child themes to factor in some of the customizations I’m putting into my main theme.<\/p>\n 2) Custom Taxonomy<\/b><\/p>\n I need to create a custom taxonomy for a specific type of post. I could manage this classification through either Categories or Tags, but that has disadvantages and would muddle things up elsewhere in the site. I could also use Custom Fields on the fly, but that wouldn’t be as easy or convenient in regular use. A custom taxonomy would give me an extra meta box with a checkbox on the post composition screen to mark these posts as they’re made. It’s more code on the back-end, but the end result is convenience. The base theme I’m building off of uses a custom taxonomy, so I should be able to modify that code to my ends then modify the loop that I currently have to pull posts from that taxonomy.<\/p>\n 3) Custom Menu\/Walker<\/b><\/p>\n Something I’ve hard-coded into the front page I think would be better handled as a custom menu. This would give me the flexibility to change the three links provided as I see fit through the WordPress menu management system rather than editing my code directly. To accomplish this, I’ll need to write a custom walker to pull post thumbnails for this “menu.” I have some example code, so this shouldn’t be more than an evening’s worth of work to code and test.<\/p>\n 4) Sticky Post<\/b><\/p>\n I’m not sure that I need and\/or want this. The base theme I’m working with implements the sticky post in an interesting way, but because I’ve created a custom homepage marking something as a sticky post has no effect. I’m not sure if it’s something I need to implement (in other words, find a place for) or if I can function without it. To be honest, I’m not sure that I need it. However, it might be better to implement it, but put a conditional on it so that if there isn’t a sticky post then that section of the homepage drops away. This will require some thought, because I’ll also have to decide where<\/i> it will go.<\/p>\n 5) Drabbles<\/b><\/p>\n How to handle these, that’s the question. They’re in a separate database in my current WordPress installation, handled by a long-out-of-date plugin called Miniblog<\/a>. I’d much rather move these into the standard WordPress database tables, but then it becomes a question of how to display them — and not<\/b> display them.<\/p>\n It’s going to require this code (from this website<\/a>), I think…<\/p>\n function exclude_categories_($toExclude) { With modifications, of course. That will get me started (and it will keep me from having to recode other loops), but I’ll also need to create a page template to handle their display in the way that I want them displayed.<\/p>\n I’m sure there’s something I’m forgetting, but those are the five big areas that are preoccupying me with the WordPress coding at the moment.<\/p>\n","protected":false},"excerpt":{"rendered":" Yes, I’ve been away. Crushing deadlines will that to a person. Tomorrow, I promise my long-awaited blog post on Star Trek: The Next Generation\/Doctor Who: Assimilation2 #4. It’s something I’ve been wrestling with for about two weeks now. At the moment, though, I’m going to write about where things are with my website redesign. 1)Continue reading “On More Coding Thoughts”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4095],"tags":[226,227,4096],"class_list":["post-6609","post","type-post","status-publish","format-standard","hentry","category-wordpress","tag-blog","tag-coding","tag-wordpress","entry"],"_links":{"self":[{"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=\/wp\/v2\/posts\/6609","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6609"}],"version-history":[{"count":0,"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=\/wp\/v2\/posts\/6609\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6609"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6609"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.allyngibson.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6609"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}add_action('pre_get_posts', 'exclude_categories_' );<\/p>\n
\n global $wp_query; \/\/ Use this variable to assign the categories to exclude
\n $categoriesExclude = '-3 -10 -11'; \/\/this is just an example. Change the ids to fit your needs
\n \/\/ this example will exclude the categories assigned to the $categoriesExclude variable
\n \/\/from homepage, archives pages, feeds but not from categories pages
\n if( is_home() || is_feed() ||( is_archive() && !is_category() )) {
\n $wp_query->query_vars['cat'] = $categoriesExclude;
\n }
\n}<\/code><\/p>\n