This is a sample that Jon Flanders put together to manage moving from page to page within a web application.  He states two goals:

1)   The WF and the ASP.NET Pages should be unaware of each other.  ASP.NET shouldn’t know it is being run by a workflow, and the workflow shouldn’t know it is being called from ASP.NET.

2)  The ASP.NET model should be preserved.  What I mean by this is that ASP.NET pages should be written using a control-based, data-bound methodology.  I also am a big fan of ASP.NET 2.0 and all the work they have done to make building pages easier.  Some other examples of using WF with ASP.NET I’ve seen make the pages go out of the regular model.  IMO – there is a reason for the page model in ASP.NET and I wanted to try to preserve that model in my integration.  So this means using server-side controls and events, along with data-binding.

You can check out his blog post on the subject here: http://www.masteringbiztalk.com/blogs/jon/PermaLink,guid,0fae3e73-7801-4cf6-a5a5-9370b0f99973.aspx