Onset Issues (3)

I have made enough progress that now I need to address content and contacts.  The later is the prickly one, and it comes in two major sub-issues.  How do I the word out to people that I am posting, and then how do I let those people know that I have put out a new post?  The content issue may be just a matter of my putting in the time, and may also be a driver of letting people know about updates.

I am currently averaging more than one post per day, and if I continue at that rate people (assuming anybody cares) can just get their “daily fix”.  Other options include getting them to use RSS, sending out email, using twitter, or some other gimmick to let them know there is something new.

There is also a question of how big each post should be, how small is too small to be worth the look, how big is too much to read at one sitting.  I am looking for comments on this.  My current guideline is for the word count to approximate 200, with a slight skew toward making larger.

How should I estimate the size of the readership?


Onset Issues (2)

This blog platform, WordPress, has room to improve, especially in the area of documentation.  Besides the packaged documentation, I have borrowed several texts from the city library, including the entries from the series: Sams Teach Yourself, For Dummies, and Smashing.

I found I wanted to do several different types of entries, publicly available chronicles (like this post), publicly available reference material (like FAQ), private notes about what I intend, and possibly others.  WP readily provides at least the three well articulated needs.  I spent too long trying to figure how to share the reference material, that is, how to throw something on the top/front page to enable easy navigation.

WP has a lovely dashboard.  The dashboard has a link to a menu manager.  The menu manager offers the ability to view and edit menus.  But I had difficulty figuring out how to place those menus for the reader to access.

WP seems to suffer from a failure that plagues the industry: the failure to state the obvious.  Here it was that WP was already showing a pair of menus on the front page.  I could not see them because they were empty, completely.  To make matters worse, these empty menus were named outside of the normal name space, so that the menu manager did not offer them for update.  To add to them, I needed to create conjure up a name for a new menu and then “locate it” in one of the existing but empty menus.  When I figured that out, I was able to produce a menu called ‘Nav’ that included links to the abstract page and the FAQ page.  Locating ‘Nav’ in the ‘primary menu’ caused it to appear, not quite where I expected it nor quite where I wanted it, but in an adequate location.


More meta posts (1)

A meta post is a post about posts.

This blog framework, like I expect all blog frameworks, will make it trivial to organise thoughts chronologically while making it difficult for readers to find threads of coherent thought.  My ideal would be the reverse, AISI the real value to be found in my work would be if coherency was maximized, allowing them to glean insights without having to wade through all of everything I manage to capture.  Besides, even if I capture something astute, that does not mean that it will be presented in its most digestible form.

I expect to tag each title to reflect the topic thread it continues.  I will look for a format to breakout the links and dependent ideas from earlier post that are foundational to each entry, as I have no way of knowing which fragments any reader has already seen.