Managing Content Labels
Managing the content references (in a pseudo-block chain) is preliminary to some additional steps that were required, logically, in order for me to continue. So this post covers what I have been up to since the last post.
As I continued to think about SEO related information, it occurred to me now was the time to provide labels for the content being rendered. In fact, it was mentioned to me during a product demo, as I recall. My brother-in-law had set up a meeting and during the demo the person attending the meeting mentioned that “item X”, was a tad ambiguous and not really useful when displaying You Tube Videos, for example.
Further to this are the Image Files and other files that do not have an entire web structure “built on top” of their existence (as in the case of YouTube), and they too did not have meaningful labels.
Many sites (especially those with high SEO rankings), as I’ve noticed do use meaningful file names for their content items, thus I decided to strip the path for for content items like (images and pdf files). In this way, the end user is presented with hopefully what is a fairly meaningful name for the content, when rendering the various files under a specific content list.
In the end, I think the solution is rather nice. Using a label for each content reference, brings together for the collection of content items in a way meaningful to the end user without overwhelming them with additional data or meta data.
Also, as things progress on this project, we can do further analysis of each file type and come up with more “meta-type” information for each file. In fact at one point certain versions of KWB extracted the MP3 title from the amazon mp3 clip, but later decided I would just jump to amazons site, for audio related content.
Well that’s all for now. Be back with more plans for KWB development.