diff --git a/exampleSite/content/docs/hosting-deployment/index.ja.md b/exampleSite/content/docs/hosting-deployment/index.ja.md index 6f55eacc..ae9afe03 100644 --- a/exampleSite/content/docs/hosting-deployment/index.ja.md +++ b/exampleSite/content/docs/hosting-deployment/index.ja.md @@ -75,7 +75,7 @@ jobs: 設定ファイルをGitHubにプッシュすると、アクションが自動的に実行されるはずです。初回は失敗するかもしれないので、GitHubリポジトリの **Settings > Pages** にアクセスして、ソースが正しいか確認してください。 `gh-pages` ブランチを使うように設定されているべきです。 -{{< screenshot src="github-pages-source.jpg" alt="Screen capture of GitHub Pages source" >}} +![Screen capture of GitHub Pages source](github-pages-source.jpg?2x=true) 設定が完了したら、アクションを再実行し、サイトを正しくビルドしてデプロイします。すべてが正常にデプロイされたことを確認するためにアクションログを参照することができます。 @@ -83,7 +83,7 @@ jobs: [Netlify](https://www.netlify.com)にデプロイするには、Netlify側に新しいデプロイサイトを作成し、ソースコードとリンクします。Netlify UIでは、ビルド設定は空白のまま、使用するドメインだけを設定する必要があります。 -{{< screenshot src="netlify-build-settings.jpg" alt="Screen capture of Netlify build settings" >}} +![Screen capture of Netlify build settings](netlify-build-settings.jpg?2x=true) 次に、サイト・リポジトリのルートに `netlify.toml` ファイルを作成します: @@ -114,7 +114,7 @@ jobs: 新しい**静的サイト**を作成し、プロジェクトのコード・リポジトリにリンクします。そして、ビルドコマンドを `hugo --gc --minify` に、公開ディレクトリを `public` に設定するだけです。 -{{< screenshot src="render-settings.jpg" alt="Screen capture of Render settings" >}} +![Screen capture of Render settings](render-settings.jpg?2x=true) あなたが変更をリポジトリにプッシュするたびに、自動的にビルドとデプロイを行います。 diff --git a/exampleSite/content/docs/hosting-deployment/index.md b/exampleSite/content/docs/hosting-deployment/index.md index 93995dd5..e0819a7c 100644 --- a/exampleSite/content/docs/hosting-deployment/index.md +++ b/exampleSite/content/docs/hosting-deployment/index.md @@ -75,11 +75,11 @@ jobs: Push the config file to GitHub and the action should automatically run. It may fail the first time and you'll need to visit the **Settings > Pages** section of your GitHub repo to check the source is correct. It should be set to use the `gh-pages` branch. -{{< screenshot src="github-pages-source.jpg" alt="Screen capture of GitHub Pages source settings" >}} +![Screen capture of GitHub Pages source settings](github-pages-source.jpg?2x=true) You should also visit the **Settings > Actions > General** section and check that the workflow permissions allow actions to make changes to your repo. -{{< screenshot src="github-workflow-permissions.jpg" alt="Screen capture of GitHub Workflow Permissions settings" >}} +![Screen capture of GitHub Workflow Permissions settings](github-workflow-permissions.jpg?2x=true) Once the settings are configured, re-run the action and the site should build and deploy correctly. You can consult the actions log to check everything deployed successfully. @@ -87,7 +87,7 @@ Once the settings are configured, re-run the action and the site should build an To deploy to [Netlify](https://www.netlify.com), create a new continuous deployment site and link it to your source code. The build settings can be left blank in the Netlify UI. You will only need to configure the domain you'll be using. -{{< screenshot src="netlify-build-settings.jpg" alt="Screen capture of Netlify build settings" >}} +![Screen capture of Netlify build settings](netlify-build-settings.jpg?2x=true) Then in the root of your site repository, create a `netlify.toml` file: @@ -117,7 +117,7 @@ Deploying to [Render](https://render.com) is very straightforward and all config Create a new **Static Site** and link it to your project's code repository. Then simply configure the build command to be `hugo --gc --minify` and publish directory to be `public`. -{{< screenshot src="render-settings.jpg" alt="Screen capture of Render settings" >}} +![Screen capture of Render settings](render-settings.jpg?2x=true) The site will automatically build and deploy whenever you push a change to your repo. diff --git a/exampleSite/content/docs/version-2/_index.ja.md b/exampleSite/content/docs/version-2/_index.ja.md index 58b8fc9b..4dd3812c 100644 --- a/exampleSite/content/docs/version-2/_index.ja.md +++ b/exampleSite/content/docs/version-2/_index.ja.md @@ -62,7 +62,7 @@ Congo 2.0の大きな変更点は、画像の自動リサイズ機能の追加 今回のアップデートでは、全体的にパフォーマンスが向上している。今回のリリースの主な目的はLighthouseのスコアを向上させることで、Congoは4つの指標すべてで100点満点を獲得しました。 -{{< screenshot src="lighthouse.jpg" >}} +![](lighthouse.jpg?2x=true) 個々の変更点が多すぎて、ここでは紹介しきれませんが、さらに詳しく知りたい場合は、[Lighthouseのレポート](lighthouse.html)をご覧ください。実際のパフォーマンスは、サーバーの構成によって異なります。 diff --git a/exampleSite/content/docs/version-2/_index.md b/exampleSite/content/docs/version-2/_index.md index 2f4c738f..d05d5386 100644 --- a/exampleSite/content/docs/version-2/_index.md +++ b/exampleSite/content/docs/version-2/_index.md @@ -62,7 +62,7 @@ Best of all there's nothing you need to change! Simply insert standard Markdown This update packs performance improvements throughout. A key objective for this release was to improve Lighthouse scores and Congo now scores a perfect 100 on all four metrics. -{{< screenshot src="lighthouse.jpg" >}} +![](lighthouse.jpg?2x=true) There's too many individual changes to highlight them here but the results speak for themselves. If you want to dig deeper, you can [view the Lighthouse report](lighthouse.html). Real world performance will vary based upon server configuration. diff --git a/layouts/shortcodes/screenshot.html b/layouts/shortcodes/screenshot.html deleted file mode 100644 index e08243ce..00000000 --- a/layouts/shortcodes/screenshot.html +++ /dev/null @@ -1,24 +0,0 @@ -{{ if .Get "src" }} - {{ $image := .Page.Resources.GetMatch (printf "*%s*" (.Get "src")) }} - - {{- if .Get "href" -}} - - {{- end -}} - - {{ $altText := "" }} - {{ with .Get "alt" }} - {{ $altText = . }} - {{ else }} - {{ $altText = (.Get "caption") | markdownify | plainify }} - {{ end }} - - {{ partial "picture.html" (dict "img" $image "alt" $altText "x2" true) }} - - {{- if .Get "href" }}{{ end -}} - {{- if .Get "caption" -}} -
- {{- .Get "caption" | markdownify -}} -
- {{- end }} - -{{ end }}