Checkout layout

Where do I change the look, fields and fonts, for the checkout pages. Billing address and Shipping address.

I have version 2.3

Look at the Views in this folder

If you have source code:

...\src\Presentation\Nop.Web\Views\Checkout


If you don't have source code

...\Views\Checkout

New York wrote:

I will have to disagree with the above statement.  If you keep all styling (not structure) in your CSS classes(Theme>Stylesheet) you will never have to worry about upgrading to new versions of nopCommerce.  If you modify the structure(the above statement would be correct) of the HTML layout upgrades will be much more difficult.

How will I change the fonts etc just for this one page?

Since I also need to change the order of some of the fields I am looking at ...\Views\Checkout. However, the order of fields in this file don't appear to be the same order as on the displayed page.

Also, if I want to change the label, such as first name, email etc., where do I do that?

I guess I should have clarified "Look at the Views in this folder".  I didn't mean to imply that all changes would be made there (although certain ones need to be - e.g. replace a text box with a drop down).  Rather, I was also implying that all the info needed for changes are in the Views - i.e. the names of the style sheet classes. E.g.

        <div class="enter-address-title">
...
        <div class="enter-address">


However, I'll have to disagree :) with
eddtech wrote:
That's not always the case.  New features added to the core can also include changes to style classes, and addition of new classes.   If you don't deal with them by either merging with, or modifying your stylesheet, then things may look funny.

Thanks for the example! I didn't notice this in the past.  +1

New York wrote:

Their has to be a way to dynamically assign CSS class(es) on a global scale, maybe resource driven.  Any ideas? This way we can continually update the back-end with incorporated scripts to update resources on the fly... Maybe that is too convenient, and out-of-bounds, but I am sure there has to be many different ways to avoid this in the future.