I sent out a Blogger invite to the following people's emails. If you see your name under the "Contributors" list, please still read this post, and please feel free to post, or comment, at will. Because of spam filtering, I have a feeling most people did not receive the email. If you find yourself on the list, please email me (thinkingfreely @ gmail) and I will re-send the invite. We need all the contributors we can get to post notices, news, and announcements relevant to the group and its activities.
I am also disclosing some posting tips for contributors below the fold. Read on...
I am also disclosing some posting tips for contributors below the fold. Read on...
The following emails have been sent a blogger invite (date/time invited):
biogenx@ufl.edu 2006-02-21 08:21:12.8
jenniferdehart@hotmail.com 2006-02-21 08:17:40.973
asilver0@ufl.edu 2006-02-26 13:53:27.326
lacivita@ufl.edu 2006-02-21 08:17:40.94
ckinter@ufl.edu 2006-02-26 03:10:47.956
bgalecki@ufl.edu 2006-02-21 08:21:12.833
So, if your email is on that list, and you want me to re-send (I know this happened with two of our contributors), or if I used the wrong email addy, please email me.
Tip on posting: When you go to post, there is some simple HTML code in the post template you need to know. If you are posting a short article (500 words or less), then you can just clear out all of the HTML code for the post and do your thing. If you are posting a long article, though, I would appreciate it if you would use these tags to "show/hide" the teaser/fullpost, respectively, to keep our page accessible. The following code is what you will see in the "Edit HTML" mode of posting, you will see *nothing* in the "Compose" mode.
In order to display the code, I had to add the extra space before and after each carrot <>, those spaces prevent the code from working:
This tag opens your "teaser" -- the first few sentences of a long post. Everything you want to appear on the main page needs to fall between this tag and its close tag < /div >
This tag opens the rest of your post -- what will appear if you click the "Read more (+/-)" link on the main page. You *must* close this tag also with a < /div >. Note that this is only relevant to the main page, and on the ItemPage, the entire post will automagically (I meant "g", not "t") display.
If you have any questions about this, see here, or this page for more, step 5.
biogenx@ufl.edu 2006-02-21 08:21:12.8
jenniferdehart@hotmail.com 2006-02-21 08:17:40.973
asilver0@ufl.edu 2006-02-26 13:53:27.326
lacivita@ufl.edu 2006-02-21 08:17:40.94
ckinter@ufl.edu 2006-02-26 03:10:47.956
bgalecki@ufl.edu 2006-02-21 08:21:12.833
So, if your email is on that list, and you want me to re-send (I know this happened with two of our contributors), or if I used the wrong email addy, please email me.
Tip on posting: When you go to post, there is some simple HTML code in the post template you need to know. If you are posting a short article (500 words or less), then you can just clear out all of the HTML code for the post and do your thing. If you are posting a long article, though, I would appreciate it if you would use these tags to "show/hide" the teaser/fullpost, respectively, to keep our page accessible. The following code is what you will see in the "Edit HTML" mode of posting, you will see *nothing* in the "Compose" mode.
< class="shortpost">
< /div >
< class="fullpost">
< /div >
In order to display the code, I had to add the extra space before and after each carrot <>, those spaces prevent the code from working:
First tag: < class="shortpost">
This tag opens your "teaser" -- the first few sentences of a long post. Everything you want to appear on the main page needs to fall between this tag and its close tag < /div >
Second tag: < class="fullpost">
This tag opens the rest of your post -- what will appear if you click the "Read more (+/-)" link on the main page. You *must* close this tag also with a < /div >. Note that this is only relevant to the main page, and on the ItemPage, the entire post will automagically (I meant "g", not "t") display.
If you have any questions about this, see here, or this page for more, step 5.
No comments:
Post a Comment