http://www.sharepointblogs.com/bmixon/archive/2004/10/18/814.aspx

SharePoint 2003 provides us the ability to manage a single document template with each document library. In many cases this is sufficient. However there are situations where I would like to be able to present users with more than one template. The following example provides one way of handling this situation.

Thanks to Bob Mixon for this clever hack that resolves a common limitation.

http://weblogs.asp.net/jan/archive/2004/11/23/268644.aspx

Some features:

Create connectable web parts
In SharePoint you can connect web parts, so they can exchange data. For example you could create a web part that displays a list of invoices, and another web part that displays the details of the selected invoice (master/detail view). Normally you’d have to create your Invoice and InvoiceDetails web parts by hand, implementing the ICellProvider and ICellConsumer interfaces (see Patrick’s excellent article about this topic). With the new version of the SmartPart you can do the same, but instead of coding everything by hand, you can create ASP.NET user controls! Just implement the ICellProviderUserControl or ICellConsumerUserControl on your user control, and you’re done.
CAS Optimization
Maxim Karpov did a great job on fine-tuning the Code Access Security for the SmartPart. For running the previous versions of the SmartPart, you’d had to increase the trust level in the web.config to WSS_Medium. In this version this is not required anymore. Of course if your user controls require a higher trust level, you can raise the trust level as usual.
Hiding the user control selection
Once you’re finished building your user controls, maybe you’d want to ship the finished web parts/user controls to a customer for example. In that case you don’t want the user to select the user controls from the dropdown listbox of the SmartPart, or filling out the user control name by hand. With the new version of the SmartPart you can create a DWP file which contains all the settings for an instance of the SmartPart showing a specific user control. The nice part is that you can hide the dropdown listbox or textbox for selecting the user control.

Thanks to Alex Lakeland for this:

1. Create a datetime column named Date (this takes the date of the news article)
2. Create a calculated column named WeekStart returning type datetime, with the calculation:
=IF(TEXT(WEEKDAY(Date),"ddd")="Mon",Date,IF(TEXT(WEEKDAY(Date-1),"ddd")="Mon
",Date-1,IF(TEXT(WEEKDAY(Date-2),"ddd")="Mon",Date-2,IF(TEXT(WEEKDAY(Date-3)
,"ddd")="Mon",Date-3,IF(TEXT(WEEKDAY(Date-4),"ddd")="Mon",Date-4,IF(TEXT(WEE
KDAY(Date-5),"ddd")="Mon",Date-5,Date-6))))))
3. Create a calculated column named WeekEnd returning type datetime, with the calculation:
=IF(TEXT(WEEKDAY(Date),"ddd")="Sun",Date,IF(TEXT(WEEKDAY(Date+1),"ddd")="Sun
",Date+1,IF(TEXT(WEEKDAY(Date+2),"ddd")="Sun",Date+2,IF(TEXT(WEEKDAY(Date+3)
,"ddd")="Sun",Date+3,IF(TEXT(WEEKDAY(Date+4),"ddd")="Sun",Date+4,IF(TEXT(WEE
KDAY(Date+5),"ddd")="Sun",Date+5,Date+6))))))
4. Create a view with the following filter:
Column: WeekStart <= [Today] AND WeekEnd >= [Today]

http://blogs.msdn.com/frontpoint/archive/2004/11/11/255773.aspx

Using Conditional Formatting and the data view opens up a whole new world of possibilities

Yes, it's so easy, just copy the pages in FrontPage and you can make as many as you want!

http://sharepoints.blogspot.com/2004/06/10-page-limit-in-meeting-workspace.html

Edit these files:

AlertAutoDeactivationNotification.xsl
AlertCreationConfirmation.xsl
AlertNewsLetterNotification.xsl
AlertResultNotification.xsl

They sit within the sharepoint portal server program directory under

DATA\Alerts\1033.

Changes to these files let me create the custom alert email I wanted.You will probably need to restart either IIS or the portal to see the changes come through.

Ryan Chomiack

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/spptsdk/html/tsptCustomAlertMsgs.asp

Portal and WSS alert emails are different.

http://www.exceltip.com/st/Using_Loops_in_VBA_in_Microsoft_Excel/628.html

I've done this myself and found this information useful. when the user opens the excel spreadsheet, the macro runs, syncs the data with SharePoint, copies the row info to columns on a different tab so the user can see it in a Printable view.

http://blogs.msdn.com/bowerm/articles/175691.aspx

Drop-down menus in Windows SharePoint Services and SharePoint Portal Server 2003 enable actions that relate to a specific document in a document library to be viewed and invoked. This article shows how these document context menus can be extended to add custom menu items. The document first explains how SharePoint document library context menus work, and then demonstrates how custom menu items can be added.

Few more options here:
https://blogs.msdn.com/jessicagruber/archive/2005/07/27/Custom_Menus_in_SharePoint.aspx