問(wèn)題描述
我正在管理一個(gè)包含大量靜態(tài) HTML 網(wǎng)站的舊網(wǎng)站，沒有服務(wù)器端腳本，只有純 HTML/CSS，最少的 javascript.我發(fā)現(xiàn)在不同頁(yè)面中多次更改同一段代碼非常浪費(fèi)時(shí)間.例如，當(dāng)菜單中的某些內(nèi)容發(fā)生更改時(shí)，由于菜單只是每個(gè)文檔中的靜態(tài)文本，因此我必須多次進(jìn)行相同的更改.
I am managing a legacy website with a lot of static HTML websites, no server side scripting, just plain HTML/CSS, minimal javascript. I found it a huge waste of time to change the same piece of code numerous times in different pages. For example, when something in the menu changes, since the menu is just static text in each document, I have to make the same change numerous times.
我想知道將這種開銷降到最低的最佳策略是什么，換句話說(shuō)，對(duì)于跨多個(gè)靜態(tài) HTML 頁(yè)面管理諸如導(dǎo)航代碼之類的事情，您會(huì)推薦什么.
I was wondering what the best tactic would be to minimize this overhead, in other words what would you recommend for managing things like navigation code across multiple static HTML pages.
我知道你可以使用:
- 服務(wù)器端腳本(如 PHP)，但沒有其他理由在該特定站點(diǎn)使用腳本.
- 框架(但這很糟糕，因?yàn)樗?.....好吧，框架:))
- 服務(wù)器端包含(似乎在更改服務(wù)器時(shí)可能會(huì)導(dǎo)致麻煩)
- javascript(不利于 SEO)
你會(huì)推薦什么?
謝謝.
推薦答案
在所有可能性中，無(wú)論是您列出的內(nèi)容還是我所知道的任何其他內(nèi)容，我仍然會(huì)使用基于 PHP 的簡(jiǎn)單解決方案來(lái)運(yùn)行.它既簡(jiǎn)單又干凈，幾乎不需要您付出任何努力.我對(duì)我設(shè)計(jì)的所有小型網(wǎng)站都這樣做.
Out of all the possibilities, both what you listed and anything else I know of, I'd still just run with a simple PHP-based solution. It's easy and clean, requiring next to no effort on your part. I do this with all the small sites I design.
大多數(shù)情況下，您會(huì)得到相當(dāng)簡(jiǎn)單的結(jié)構(gòu).您寫了一整頁(yè)，然后對(duì)于每個(gè)后續(xù)頁(yè)面，您只需更改內(nèi)容所在的中間部分.在這種情況下，只需將內(nèi)容上方和下方的所有內(nèi)容保存在 header.php 和 footer.php 文件中，然后放入 在每個(gè)內(nèi)容文件的頂部(與頁(yè)腳文件類似).完成！
Most often, you end up with fairly trivial structure. You write up a full page, then for each subsequent page you're just changing the bit in the middle where the content lives. In that case, just take everything above and below the content and save it in header.php and footer.php files, then put <?php require_once "header.php"; ?> at the top of each content file (and similarly with the footer file). Done!
這確實(shí)有一些小缺點(diǎn).一方面，您依賴于腳本，但 PHP 是世界上部署最廣泛的服務(wù)器端語(yǔ)言，所以這不是一個(gè)真正的問(wèn)題.你甚至不在乎它是 PHP4 還是 PHP5，因?yàn)槟銢]有做任何花哨的事情.
This does have some minor disadvantages. For one, you're depending on scripting, but PHP is the most widely deployed server-side language in the world, so that's not really an issue. You don't even care if it's PHP4 or PHP5, since you're not doing anything fancy.
對(duì)于兩個(gè)，您在每次頁(yè)面加載時(shí)都運(yùn)行一個(gè)腳本，以便提供本質(zhì)上是靜態(tài)文件的內(nèi)容.這會(huì)減慢您的響應(yīng)速度，并對(duì) CPU 造成不必要的壓力.這可能無(wú)關(guān)緊要(滯后非常小)，但如果您發(fā)現(xiàn)它很浪費(fèi)，那么有一些很好的 PHP 框架可以為您提取 PHP 生成的頁(yè)面并從中生成靜態(tài) html.(這也很容易自己做，只需使用輸出緩沖做一些工作.)這樣你就可以兩全其美 - PHP 模板(如果你最終想要更花哨的東西，還可以使用完整的 PHP 語(yǔ)言) 但靜態(tài) html 頁(yè)面可實(shí)現(xiàn)最少的 CPU 活動(dòng)和最快的頁(yè)面加載時(shí)間.
For two, you're running a script on every page load, in order to serve what is essentially a static file. That slows down your responses, and stresses the CPU unnecessarily. This probably doesn't matter much (the lag is very minor), but if you find it wasteful, there are some good PHP frameworks which will take your PHP-generated pages and generate static htmls out of them for you. (This is easy enough to do yourself, too, with just a bit of work using output buffering.) This way you get the best of both worlds - PHP templates (and the full PHP language if you end up wanting something fancier down the line) but static html pages for minimal CPU activity and fastest page load times.
這篇關(guān)于管理靜態(tài) HTML 網(wǎng)站中重復(fù)代碼的最佳方法是什么的文章就介紹到這了，希望我們推薦的答案對(duì)大家有所幫助，也希望大家多多支持html5模板網(wǎng)！