Home/ Questions/Q 63127
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T18:35:02+00:00

I need to build a prototype for an intranet website, and I want to

  • 0

I need to build a prototype for an intranet website, and I want to focus on usability (layout, navigability, etc) and leave the theme for later (I have very bad taste, so this will probably be done by someone else)

I know about ASP.NET’s capability of switching themes instantly, but how do I have to design the WebForms for it to be easy later?

  • Should I create controls with a class attribute pointing to something that will exist in the future css?
  • Or do I simply create the controls without worrying about this and it’ll be handled easily when we create the theme?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. If you’re planning on using ASP.NET Themes, then you can design all of the controls generically and add Skins later on. Depending on the complexity of the design (meaning how many different styles you have for textboxes or gridviews, etc), this might not save you a lot of work, but it’s one way to use the built-in .Net support for theming.

    Make sure you use a MasterPage so that all of your sub pages will have a common base, and give all of your elements good IDs, because you will still need to get your hands dirty with CSS to put it all together.

    Here’s a link to a decent Themes & Skins tutorial. Knowing what you’ll have to do in the future to add this in will make it easier to design for it now.

    • 0