The state of the newsletter
Mar. 5th, 2008 04:50 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Hi editors :-)
Another week, another newsletter. I wrote in the newsletter that next week's will be published Sunday, because that way I'll be able to take advantage of the auto posts, which should hopefully save me some work.
The thing is, I can't continue to edit by hand, because working with the mouse is too painful for me.
These are our options:
I really can't emphasize this enough: If we continue to use diigo, we must be absolutely consistent with tags and careful to avoid code borking, because otherwise there is a lot of editing that must be done before the newsletter is ready to post.
This coming Sunday when diigo auto posts, I'll try marking all the bookmarks as private rather than deleting them. I don't know how often diigo's cache refreshes, but hopefully all the old links won't be posted again next week. It's the only way I can think of to try to keep the tags consistent, because then diigo knows to suggest a tag based on the first few key strokes.
Another week, another newsletter. I wrote in the newsletter that next week's will be published Sunday, because that way I'll be able to take advantage of the auto posts, which should hopefully save me some work.
The thing is, I can't continue to edit by hand, because working with the mouse is too painful for me.
These are our options:
- Use a perl script to format the newsletter. There is a perl script for formatting the auto post which delicious generates. It has the same problem with text encoding which diigo has, and what's more it requires a perl engine. My website is hosted on someone else's site, so that's not an option. Do any of you have a website with perl?
- Each of us can edit our links into a template by hand. Since we now have the
white_collar_roundup dw, it should be easier than using google docs was. At least for me, google docs crashed constantly and the text field was so tiny I could barely see what I was doing. The huge disadvantage to this option would be that it takes time to scroll up and down looking for the categories, and it would involve either coding which I know is tedious and easy to mess up with a single typo, or it would involve saving to diigo and then exporting the links and re-formatting them, which is also very tedious but at least means a smaller risk of typos.
- We can continue using diigo. But if we do, we have to be very careful with how we fill in the description and tags, otherwise it won't work:
- At the end of each line there should be an html linebreak<br>
not both an html linebreak and an actual linebreak that you can see on your screen
and no linebreak at the end of the last line or before the beginning of the first line - we have to be very strict about removing all special characters, because we don't know yet which of them are messing up the text encoding
- no apostrophes in tags
- we have to use consistent category tags, because diigo can't tell that "episode.reaction" and "episode_review" are the same category, or "p.neal_kate" and "p.kate_neal".
- If you add a new tag you must also add a new auto post for that tag or include a category tag which has already been added as an auto post.
- We should avoid white space because the layout is very difficult to read, and the spacing is really the only thing visually tying one entry together and distinguishing it from the next.
- At the end of each line there should be an html linebreak<br>
- Or, someone other than me can do the final editing and formatting of the newsletter.
I really can't emphasize this enough: If we continue to use diigo, we must be absolutely consistent with tags and careful to avoid code borking, because otherwise there is a lot of editing that must be done before the newsletter is ready to post.
This coming Sunday when diigo auto posts, I'll try marking all the bookmarks as private rather than deleting them. I don't know how often diigo's cache refreshes, but hopefully all the old links won't be posted again next week. It's the only way I can think of to try to keep the tags consistent, because then diigo knows to suggest a tag based on the first few key strokes.
(no subject)
Date: 2010-03-05 09:09 pm (UTC)I found diigo faster, only if I could just copy and remove the formating that you get off of the AO3, editing it is a pain.
I would be happy to do the assembly. I would likely do it Friday afternoon my time which is UST - 5 hours. Do we want to stick with diigo for another week and see how it goes? I could collect everything off of diigo on Friday, make a post on white_collar_roundup with the links there, edit it to look nice and put the cuts in, and then, do we want to just post it on Sunday since we said we would?
If we go that route than we need everyone to go back to doing the diigo bookmarks without any html in them.
(no subject)
Date: 2010-03-05 09:52 pm (UTC)I think you should post Friday since that's what's most practical for you and that's what we're all used to. I can just edit the newsletter and strike out the thing about Sunday.
(no subject)
Date: 2010-03-07 03:27 pm (UTC)(no subject)
Date: 2010-03-07 05:33 pm (UTC)