What is the best way to build static web site for product catalogue with maintainable in mind

Discussion in 'HTML & Website Design' started by ketting00, Nov 8, 2016.

  1. #1
    Hey guys,
    I need your help. Any inputs would be counted.

    Some times ago and it's not very long time. :)
    I've built a static web site for a friend of my friend's product catalogue. She sells tailored-made pillow, mattress and cushion, something like that.

    Since she knows nothing about the internet other than a regular user I thought I would use simple static html scheme, a kind of put it online and forgot. So every html file would be built on this structure:

    
    <!DOCTYPE html>
    <html>
    
        <head>
            <meta name="viewport" content="width=device-width,initial-scale=1,minimum-scale=1,maximum-scale=1,user-scalable=yes">
            <meta charset="UTF-8">
            <title>My Web Site</title>
            <link rel="stylesheet" type="text/css" href="css/style.css" />
        </head>
     
        <body>
            <div>
                <!-- skipping header, footer -->
                Content container where products are listed here, depending on the individual products page or categories page.
            </div>
        </body>
     
    </html>
    
    Code (markup):
    Bad enough, her products sold like hotcakes and she even got an export business in just couple of months. Her customers told her that they've come from the internet. (I knew how SEO works.)

    My problem is: any times she got new products or even new colors to add to the web site she would come to me and requested helping for an update.

    There are well over 200 static html files and they contain links to one another (breadcrumb, sidebar, everywhere). Each time I've got to edit one file I have had to edit dozens of them altogether. And that's just for one new color added.

    So, how do you make it easier to maintain if you are going to throw the old one away and rebuild the new one from scratch.

    My criteria:

    1. I would not use scripting language like PHP, except for JavaScript, so forget about the database. The owner won't use it and I don't want to go that route either.
    2. It should be easy to update manually.
    3. My goal remain the same, put it online and forget.
    4. I'll put it on Google Firebase to make the most out of Google and spent my vacation peacefully without worrying to receive a phone call requesting for web site update as she called it.

    Thanks in advance,

    PS: Link is not available. I forgot to renew it for her until I got a phone called asking why her sale is dropped and she found her web site was not there.
    This is quite an annoyed customer but I can't just ignore her due to complicated relationship.
     
    ketting00, Nov 8, 2016 IP
  2. hdewantara

    hdewantara Well-Known Member

    Messages:
    538
    Likes Received:
    47
    Best Answers:
    25
    Trophy Points:
    155
    #2
    Hi.
    I remember of using SSI (server side include) which may help reduce the burden, a bit. But that was very long time ago. Not sure whether it can still be used safely today. Perhaps use a "javascript emulated include" ? Just an idea...
     
    hdewantara, Nov 8, 2016 IP
  3. ketting00

    ketting00 Well-Known Member

    Messages:
    782
    Likes Received:
    28
    Best Answers:
    3
    Trophy Points:
    128
    #3
    Thank you, I never heard of it.
     
    ketting00, Nov 8, 2016 IP
  4. sarahk

    sarahk iTamer Staff

    Messages:
    28,808
    Likes Received:
    4,534
    Best Answers:
    123
    Trophy Points:
    665
    #4
    I'm not sure that you do. Static sites have no advantage from an SEO perspective.

    If you want your friend to be able to update the site then you need a CMS of some sort. There are noSQL systems but noSQL is still a "database".

    Having server side scripts is practical and sensible and requires no more support than a static site would.
     
    sarahk, Nov 8, 2016 IP
    kk5st likes this.
  5. kk5st

    kk5st Prominent Member

    Messages:
    3,497
    Likes Received:
    376
    Best Answers:
    29
    Trophy Points:
    335
    #5
    In the case described in the OP, I'd say maintenance would be considerably less with server-side scripting and a database.

    This is a good case for a fairly simple bespoke CMS, one that could be easily expanded to include inventory/order control, online orders, cost-base pricing, invoicing, shipping &c.. Data entry could be easily handled through common html based forms that would absolutely not intimidate anyone at all capable of running a lemonade stand.

    cheers,

    gary
     
    kk5st, Nov 8, 2016 IP
  6. ketting00

    ketting00 Well-Known Member

    Messages:
    782
    Likes Received:
    28
    Best Answers:
    3
    Trophy Points:
    128
    #6
    We did write everything we can think of to make sure that Google bot would find us if a user search for certain keywords. It works well. We've tested it on multiple devices multiple locations different times. The web site appeared on the first page for several keywords search and it appeared on image search. I assumed that is a success.

    Again, thanks for suggestion. I'm tempted to consider CMS a bit more now.

    I'm thinking about it. Thanks,
     
    Last edited by a moderator: Nov 8, 2016
    ketting00, Nov 8, 2016 IP