我一直在閱讀AMP的可能性,但我似乎無法理解爲什麼我的頁面沒有顯示,就像Google在其演示中顯示的那樣(請參閱http://g.co/amp)。我的正常的網頁是這樣的:AMP-html頁面在Google搜索中沒有按照預期顯示
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>An example of an AMP Project; a part of a self-writen paper about maintainability</title>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta name="language" content="NL"/>
<meta name="description" content="Every software engineering project has a certain degree of maintainability. Period.">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"/>
<link rel="amphtml" href="http://amptest.millerpreview.nl/indexamp.html">
<link rel="canonical" href="http://amptest.millerpreview.nl/index.html">
</head>
<body>
<header>
<nav>
<ul>
<li><a href="/">Home</a></li>
<li><a href="/">Another page</a></li>
<li><a href="/">Another other page</a></li>
</ul>
</nav>
<h1>Welcome!</h1>
<img src='http://portal.tugraz.at/portal/page/portal/Files/internationales/Welcome_Center/Welcome_Fotolia_62393747_XXL.jpg' />
</header>
<h2>Maintainability of an Open Source Software Engineering Project</h2>
<p>
<b>Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability. In this paper, the maintainability of a randomly chosen open source Android application called TeamTalk is measured with the SIG Maintainability Model, created by the Software Improvement Group. The conclusion of the paper is an advice on improving maintainability towards the creators of this application.</b>
</p>
<h3>Introduction</h3>
<p>
Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability \cite{Heitlager07}. Maintainability is an often forgotten software quality attribute \cite{Radatz90, Swanson76} but a rather important one. Approximately 40 - 80\% of software`s life cycle is spent on maintainability \cite{Coleman94, Dubey11, Kiewkanya05}. Maintaining an application will cost less time and thus less money if the maintainability is given proper attention.<br />
<br />
The goal of this paper is to gain insight into the maintainability of a randomly chosen open source application; in this case, it is the Android \cite{Android} app TeamTalk \cite{TeamTalk}. For this, we will measure the software quality attributes \cite{ISO} of maintainability; the analyzability, changeability, stability and testability.<br />
<br />
In section 2 we will give more insights about the background of the app TeamTalk and about what the SIG Maintainability Model is. In section 3 the used tools and the approach, based on the SIG Maintainability Model, will be discussed. Section 4 shows and discusses the results, on which an overall adice is given in section 5. The paper will be concluded with a summary of the results and what our advice is for the TeamTalk developers.<br />
</p>
<footer>
<img src='http://www.greetingsfromheart.com/images/bye_bye/bye_bye.gif' />
</footer>
</body>
</html>
我的AMP html頁面是這樣的:
<!doctype html>
<html amp lang="en">
<head>
<meta charset="utf-8">
<title>Hello, AMPs</title>
<link rel="canonical" href="http://amptest.millerpreview.nl/index.html" />
<meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
<meta name="description" content="Every software engineering project has a certain degree of maintainability. Periods.">
<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "ScholarlyArticle",
"headline": "Maintainability of an Open Source Software Engineering Project",
"datePublished": "2015-10-07T12:02:41Z",
"image": [
"logo.jpg"
]
}
</script>
<style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
<style amp-custom>
main {
margin: 0 auto;
max-width: 620px;
}
</style>
<script async src="https://cdn.ampproject.org/v0.js"></script>
</head>
<body>
<main>
<header>
<nav>
<ul>
<li><a href="/">Home</a></li>
<li><a href="/">Another page</a></li>
<li><a href="/">Another other page</a></li>
</ul>
</nav>
<h1>Welcome!</h1>
<amp-img src='http://portal.tugraz.at/portal/page/portal/Files/internationales/Welcome_Center/Welcome_Fotolia_62393747_XXL.jpg' width="325" height="200"/>
</header>
<h1>Maintainability of an Open Source Software Engineering Project</h1>
<p>
<b>Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability. In this paper, the maintainability of a randomly chosen open source Android application called TeamTalk is measured with the SIG Maintainability Model, created by the Software Improvement Group. The conclusion of the paper is an advice on improving maintainability towards the creators of this application.</b>
</p>
<h3>Introduction</h3>
<p>
Every software engineering project has a certain degree of maintainability which is directly derivable to the quality of the software, the complexity of the code, the amount and quality of the documentation and the understandability \cite{Heitlager07}. Maintainability is an often forgotten software quality attribute \cite{Radatz90, Swanson76} but a rather important one. Approximately 40 - 80\% of software`s life cycle is spent on maintainability \cite{Coleman94, Dubey11, Kiewkanya05}. Maintaining an application will cost less time and thus less money if the maintainability is given proper attention.<br />
<br />
The goal of this paper is to gain insight into the maintainability of a randomly chosen open source application; in this case, it is the Android \cite{Android} app TeamTalk \cite{TeamTalk}. For this, we will measure the software quality attributes \cite{ISO} of maintainability; the analyzability, changeability, stability and testability.<br />
<br />
In section 2 we will give more insights about the background of the app TeamTalk and about what the SIG Maintainability Model is. In section 3 the used tools and the approach, based on the SIG Maintainability Model, will be discussed. Section 4 shows and discusses the results, on which an overall adice is given in section 5. The paper will be concluded with a summary of the results and what our advice is for the TeamTalk developers.<br />
</p>
</main>
</body>
</html>
它這樣表示在谷歌搜索,並在AMP演示。我知道我的網頁是由Google緩存的:https://cdn.ampproject.org/c/amptest.millerpreview.nl/indexamp.html。在本地,我的AMP已經過驗證,但在緩存版本中,它表示腳本標記無效,即使這是AMP引擎javascript,應該視爲有效。
我的問題;這是不是還沒有在谷歌搜索實施,或者我做錯了什麼?
我的谷歌搜索結果看起來是這樣的:
請不要看內容;我只需要快速設置一個儘可能簡單的例子。我甚至無恥地添加了我在Google上發現的最醜陋的圖像,僅僅是出於測試的原因。 –