About the blog platform . The Appropedia blog is based on Wordpress.

Skin[edit | edit source]

Development[edit | edit source]

In a rough order of priority, our wants are listed below. if you have a suggestion, please edit the entry or add a comment - thank you!

  1. Set up a newsletter. Best leads so far are MailPress and this old blog post by Lorelle on WordPress (written pre-MailPress). (Our notes so far are at Appropedia:Newsletter/Software and setup but that might be a distraction). For more on MailPress, see the WordPress.org plugin page, which gives a different angle, explaining how it works in a modular way (or that's what it looks like.) Update: It looks like MailChimp offers important marketing features (e.g. knowing who is actually opening the newsletter and following links), so we'll be better to go with that. It also means not waiting for our tech development to find the resources to do this. --Chriswaterguy 21:11, 28 August 2012 (PDT)
  2. Set the character set. Our flickr plugin warns that we have not set our character set... and that we should set it to utf8. (Does that sound right? Will that let us blog in, say, French and Spanish? We think it should works for most languages, could be wrong.) (Note: The blog is set to UTF8. At least, the source code and Wordpress config both think so. Zak 18:12, 27 April 2009 (UTC))Reply[reply]
  3. Link the author name for blog posts (and comments for logged in users) to their wiki userpage, https://www.appropedia.org/User:Username Done by Zak 23:41, 5 March 2009 (UTC)Reply[reply]
  4. Fix the feed - see the errors on feedvalidator.org.
  5. :* rebugger on Identica gave this feedback: line 162 in your feed: he doesn't like onClick - and the blankline: check your feedgenerating phpfile (Fixed Zak 18:56, 27 April 2009 (UTC))Reply[reply]
  6. Make an Indonesian blog. As a guess, this might be a matter of
    1. using categories for languages(Done There are categories for English and Bahasa Indonesia. To add other languages, just add child categories of the Language category. The wiki is set up so that new languages will be automatically displayed in the navigation as they are added. Zak 22:03, 27 April 2009 (UTC))Reply[reply]
    2. making English the default (Done I've renamed uncategorized to English and made it a child of Language. This should make it the default for pages that we forget to categorize. Zak 22:03, 27 April 2009 (UTC))Reply[reply]
    3. making the front page just display the English category; and (Done Only english categorized posts show on the front page. Zak 22:03, 27 April 2009 (UTC))Reply[reply]
    4. making a new page to display pages in the Indonesian category. (Todo: Chris will need to add a new template file to the site for Indonesian. As long as it is called category-188.php, it will be automatically used when people view the Bahasa Indonesia category. We may want to make some other tweaks to the main template to that it is localized. Zak 22:03, 27 April 2009 (UTC))Reply[reply]
  7. Integrated login with the wiki. (Note: A good option might be to use OpenID for both the wiki and the blog. Zak 18:12, 27 April 2009 (UTC). Sounds good - I'm also thinking about cross-login between relate sites - Appropedia and partners, esp those that will be using Appropedia via an API. OpenID in its current form seems like it's asking for phishing attacks, but could we make use of OpenID as the mechanism, with automatic approval between a certain set of sites? Will that work? --Chriswaterguy 18:09, 24 May 2009 (UTC))Reply[reply]
  8. Plugin that sorts definite spam from probable spam. (If it has multiple links and sexual terms, I'd rather let the filter call it definite spam, and just bin it.) (Note: Akismet isn't sufficient for this? It gets most of my blog spam. Zak 18:12, 27 April 2009 (UTC) Note: Looking at my own configuration, I can see that the Bad Behaviour plugin catches lots and lots of the blog spam. Zak 22:03, 27 April 2009 (UTC). Solved - you're right, Bad Behaviour is wonderful for turning the deluge of spam to be checked into a trickle. --Chriswaterguy 18:09, 24 May 2009 (UTC))Reply[reply]
  9. Plugin to add "Related posts" from our own blog, to each post? Is this a good idea? e.g. this one - http://mitcho.com/code/yarpp/ - finds content within your site. (and http://wordpress.org/extend/plugins/wordpress-23-related-posts-plugin/ ?) Ideally we could find wiki pages as well. If both WP & MW use SQL, that might be possible...? (Note: My experience with related post plugins is that they generate extra noise. Consistently using a clear set of tags and categories across the blog and wiki (and a bit of blog/wiki re-jigging) provides a better experience for the user. Zak 18:12, 27 April 2009 (UTC) - Looks like you're right. I tried one but have deactivated it. Interested in what you have in mind by blog/wiki re-jigging. --Chriswaterguy 18:09, 24 May 2009 (UTC))Reply[reply]
  10. Add a license notice, esp the CC-BY-SA mark. (We need to work out the details, but it will include CC-BY-SA, and maybe GFDL, with a note that some quoted content is "fair use" and the onus is on the user to check this). (Note: Once this is figured out, it is fast to do. Zak 18:12, 27 April 2009 (UTC)) License is sorted, since we've now changed the wiki to CC-BY-SA, and GFDL is unnecessary. I've used a plugin, but will switch to adding some code to the footer.php, mentioning the fair use thing. --Chriswaterguy 18:09, 24 May 2009 (UTC)Reply[reply]

Points to note[edit | edit source]

  • We want to have a consistent look and feel, between the blog and the wiki. The wiki skin also needs to be developed - see Appropedia:Skin.

Plugins[edit | edit source]

Suggestions for good plugins? Add them here:

See also[edit | edit source]

Discussion[View | Edit]

Cookies help us deliver our services. By using our services, you agree to our use of cookies.