angular-docs-cn/aio/content/file-not-found.md

<div class="center-layout-wide">
  <div class="nf-container l-flex-wrap flex-center">
    <img src="assets/images/support/angular-404.svg" width="300" height="300"/>
    <div class="nf-response l-flex-wrap">
      <h1 class="no-anchor no-toc">Page Not Found</h1>
      <p>We're sorry. The page you are looking for cannot be found.</p>
    </div>
  </div>
  <aio-file-not-found-search></aio-file-not-found-search>
</div>
fix(docs-infra): increase the max width of the `file-not-found` page (#41275) Previously, the max width of the `file-not-found` page was limited to 50rem (800px by default). This allowed little space for showing potentially helpful search results, which are shown in columns). This commit increases the max width of the `file-not-found` page to 84rem (1344px by default) to allow search results to be visible without requiring scrolling. This will not negatively affect UX, because the page uses a multi-column layout and therefore there will rarely be long lines of text to scan. PR Close #41275 2021-03-19 13:29:52 +02:00			`<div class="center-layout-wide">`
			`<div class="nf-container l-flex-wrap flex-center">`
docs(aio): image sweep (#16609) * fix(aio): allow code blocks to clear floated images Previously the negative margin on the code headings were causing floated images to overlay the start of a code block. Now all code block successfully clear all floated elements. * feat(aio): add a `.clear` class for clearing floating images * fix(aio): tidy up image styles The css rules for `img.right` and `img.left` allow authors easy access to floating an image on the left or right, respectively. The `.image-display` rule which was always found on a figure has been simplified so that all figures have this styling. It is very unlikely that a figure will be used outside the content area; and at this time it seems like `figure` is as good an indicator that we want this kind of styling as anything. Now that images are all tagged with width and height values, we cannot assume to modify these dimensions via CSS as it can cause the image to lose its correct proportions. Until we find a better solition we must set `height` to `auto` when the screen width is below 1300px to ensure that these images maintain their proportions as they get shrunk to fit. * docs(aio): general tidy up of image HTML in guides Previously, the guides have a lot of inline image styling and unnecessary use of the `image-display` css class. Images over 700px are problematic for guide docs, so those have been given specific widths and associated heights. * docs(aio): use correct anchor for "back to the top" link The `#toc` anchor does not work when the page is wide enough that the TOC is floating to the side. * build(aio): add `#top-of-page` to path variants for link checking Since the `#top-of-page` is outside the rendered docs the `checkAnchorLinks` processor doesn't find them as valid targets for links. Adding them as a `pathVariant` solves this problem but will still catch links to docs that do not actually exist. * fix(aio): ensure that headings clear floated images * fix(aio): do not force live-example embedded image to 100% size This made them look too big, generally. Leaving them with no size means that they will look reasonable in large viewports and switch to 100% width in narrow viewports. 2017-05-09 23:53:32 +01:00			`<img src="assets/images/support/angular-404.svg" width="300" height="300"/>`
feat(aio): page not found layout and designs (#16089) Add 404 svg image h1 custom styling PR Close #16089 2017-04-16 20:19:39 -07:00			`<div class="nf-response l-flex-wrap">`
fix(docs-infra): increase the max width of the `file-not-found` page (#41275) Previously, the max width of the `file-not-found` page was limited to 50rem (800px by default). This allowed little space for showing potentially helpful search results, which are shown in columns). This commit increases the max width of the `file-not-found` page to 84rem (1344px by default) to allow search results to be visible without requiring scrolling. This will not negatively affect UX, because the page uses a multi-column layout and therefore there will rarely be long lines of text to scan. PR Close #41275 2021-03-19 13:29:52 +02:00			`<h1 class="no-anchor no-toc">Page Not Found</h1>`
			`<p>We're sorry. The page you are looking for cannot be found.</p>`
feat(aio): page not found layout and designs (#16089) Add 404 svg image h1 custom styling PR Close #16089 2017-04-16 20:19:39 -07:00			`</div>`
fix(docs-infra): increase the max width of the `file-not-found` page (#41275) Previously, the max width of the `file-not-found` page was limited to 50rem (800px by default). This allowed little space for showing potentially helpful search results, which are shown in columns). This commit increases the max width of the `file-not-found` page to 84rem (1344px by default) to allow search results to be visible without requiring scrolling. This will not negatively affect UX, because the page uses a multi-column layout and therefore there will rarely be long lines of text to scan. PR Close #41275 2021-03-19 13:29:52 +02:00			`</div>`
			`<aio-file-not-found-search></aio-file-not-found-search>`
fix(aio): do not create ToC for `file-not-found` and `fetching-error` documents Related to #16078. 2017-04-28 13:50:20 +03:00			`</div>`