Monthly is a better idea, I like the idea of having a newsletter. :)

Well you will be able to join our internal newsletter discussion after the merge :p

I think that monthly would be great too. Every 14 says would be fine also, but given the size of this site a little too much work me thinks.

Though it would be nice to tie it in with the hack of the month poll. Probably release it about a week or two before the poll closes, that way we all have time to install the hacks and post and informed opinion.

well, we'll see, stay cool ;)

I have a solution to this. Sending emails can be hell for vb.org. They could get 1000's of Mailor Demon requestbacks. I would say the server load for sending 60,000 members an email every 14 days would be much also. Plus I myself get enough email from people, no more please. Also, lets say i got the email on the 1st, and on the 9th i want to know the newest releases? I don't want to have to wait 5 days just to get an answer.

Solution. Make a new file like latesthacks.php or something. With drop down menus selecting vB2 or vB3. Which forums, and how many days would you like to check. So the user can pick a vb3 hack in all subforums for the last 3 days. Ect... Hope you see where i'm getting at.

Hope my idea is helpful

While this is also a good idea, I think alot of this can be done simply using the search or the external.php for xml/rss.

The newsletter would probably be something to give members that don't check in that often a quick update.

i have plans to make the portal page more customizable in the future, so that might help you as well Ken.

Still as colin said, a newsletter is a different thing, other informations can come up there.
Also just a minority of those 60k members are licensed ;)

Now information about how to do that would be most useful. I have created a very very basic customizable portal page, but am not 100% happy with my coding or with the results. Once you have released it here, any chance of letting others in on the how to?s and wherefores?

Well currently i just have some ideas, no idea if i can do everything like i want it to be.

also it would be coded into the vb.org portal and therefore won't work alone.

The main thing behind is right now to not increase the ammount of queries, but making the whole portal more customizalbe and less cluttered regarding the merge of vbt and vb.org and other future changings