Community archive

Ask something
Discussion Locked

Calling all bloggers

0 helpful
7 replies

by smorty71

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are putting the finishing touches on the first phase of our new blogging tools.

For those of you with an existing blog (say on Blogger), you can use your Blogger RSS feed to import your external blog into TR. Once you do that, TR members will be able to read and comment on your posts. If there are posts in your external blog that aren't appropriate for TR, you can delete individual items. Also, you can add new items with the TR tool that will intermingle with your imported blog (is this getting confusing yet?).

For those without a blog, you can start a new one with the TR blogging tools.

As with new discussion threads, you will be able to tag your blog posts.

We'll send out an official notification some time tomorrw; however, in the meantime, think about your first blog post.

Let me know if you have any questions,
sm

7 replies

by oz_media

Um, errrrrr....um, if we...if, if if we have, no tht's not it. Um, er, if .....

Ah whatever, thanks for the mug! :)

by house

I don't think that I'll be migrating any of my blogs over to TR. Perhaps, I will keep a simple 'work related' journal of sorts, but other blogs that I have out there may not really fit in with the point of this site.

by smorty71

The whole idea of importing was just to help out those who already had IT-related blogs and didn't want to duplicate their efforts.

We would love for you to be able to contribute your IT thoughts in a TR blog.

We pushed back the launch to this Tuesday. We'll post again when they're live.

sm

by apotheon

I've got a couple of feature requests:

1. We need some kind of notification of unread comments to our blog posts. Well, I need it, anyway. I'd really like to be able to keep up with comments people leave for my blog posts without having to remember how many comments there were on every single one of my blog entries and scroll through the whole list to see if any have changed. It's still manageable for me to do that at this point, but I rather suspect it won't be for much longer. This notification should not just take the form of email alerts, either: some of us won't want email alerts for blog comments (and by "some of us" what I really mean is "I"). It should be a relatively trivial thing to create some kind of aggregator script that tracks visited comments, I would thing, though it may involve cookies. It's difficult for me to judge how easy something like this would be without seeing the source code for the site, unfortunately, and if the relevant code is all in Java I doubt I'd want to look at it anyway. Heh.

2. As I think I might have mentioned elsewhere, it would be nice to be able to delete comments. In particular, I'd like to see the ability to delete/edit one's own comments, and the ability to delete (but not edit) comments left by others in one's own blog. This last option, deleting comments left by others, is of particular import in case of spamming activity in blog comments.

Thoughts? Questions? Comments?

by Jay Garmon

The Edit Comments feature is in the pipeline, as is a comment notification e-mail alert. In the short term, we're going to roll out an improved blog post form with some WYSIWYG functionality.

by apotheon

Will there be any way to track new comments outside of an email alert? Will I still be able to use CSS in my posts? I really rather like being able to format my blog posts so that they get justified text rather than left-aligned, and I'll probably eventually find other things to do that I wouldn't be able to with the probable features of a WYSIWYG-only editing interface.

by apotheon

This whole TR blog thing is great fun.

Is there any way we could get some kind of checkbox or radio button in our profile or blog settings that will allow us to have the code view by default when editing/posting in the blog? When I go to edit, it seems to actually parse the raw code, then display it, and when I click on the button to go back to a source view it derives the source from what was displayed when the code was parsed, which ends up rewriting my source.

This isn't a huge problem, but it raises to issues:

1. It inserts hard linebreaks so that the source formatting is extremely ugly. No biggie, but still. . . .

2. It strips inline CSS out of the source, so that I have to enter it again every time I go to edit a post.

This discussion is closed to new replies.