mirror of
https://github.com/tiennm99/hugoDocs.git
synced 2026-10-14 08:18:30 +00:00
Docs: move tutorial screenshots in their own subfolder
This commit is contained in:
1 parent
4b3a2695a3
commit
8c63a2238b
17 files changed
+16
-16
No files matched your search
@@ -68,7 +68,7 @@ If everything is fine, you should be able to see something similar to the image
|
||||
|
||||
![][1]
|
||||
|
||||
[1]: /img/tutorials/creating-a-basic-hugo-site.png
|
||||
[1]: /img/tutorials/automated-deployments/creating-a-basic-hugo-site.png
|
||||
|
||||
## Setting up version control
|
||||
|
||||
@@ -109,7 +109,7 @@ git push -u origin master
|
||||
|
||||
![][2]
|
||||
|
||||
[2]: /img/tutorials/adding-the-project-to-github.png
|
||||
[2]: /img/tutorials/automated-deployments/adding-the-project-to-github.png
|
||||
|
||||
## Welcome to wercker
|
||||
|
||||
@@ -117,7 +117,7 @@ Let's start by setting up an account for Wercker. To do so we'll go to http://we
|
||||
|
||||
![][3]
|
||||
|
||||
[3]: /img/tutorials/wercker-sign-up.png
|
||||
[3]: /img/tutorials/automated-deployments/wercker-sign-up.png
|
||||
|
||||
## Register
|
||||
|
||||
@@ -125,7 +125,7 @@ To make life easier for ourselves, we will then register using GitHub. If you do
|
||||
|
||||
![][4]
|
||||
|
||||
[4]: /img/tutorials/wercker-sign-up-page.png
|
||||
[4]: /img/tutorials/automated-deployments/wercker-sign-up-page.png
|
||||
|
||||
## Connect GitHub/Bitbucket
|
||||
|
||||
@@ -133,7 +133,7 @@ After you are registered, you will need to link your GitHub and/or Bitbucket acc
|
||||
|
||||
![][5]
|
||||
|
||||
[5]: /img/tutorials/wercker-git-connections.png
|
||||
[5]: /img/tutorials/automated-deployments/wercker-git-connections.png
|
||||
|
||||
## Add your project
|
||||
|
||||
@@ -141,7 +141,7 @@ Now that we've got all the preliminaries out of the way, it's time to set up our
|
||||
|
||||
![][6]
|
||||
|
||||
[6]: /img/tutorials/wercker-add-app.png
|
||||
[6]: /img/tutorials/automated-deployments/wercker-add-app.png
|
||||
|
||||
## Select a repository
|
||||
|
||||
@@ -149,7 +149,7 @@ Clicking this will make Wercker show you all the repositories you have on GitHub
|
||||
|
||||
![][7]
|
||||
|
||||
[7]: /img/tutorials/wercker-select-repository.png
|
||||
[7]: /img/tutorials/automated-deployments/wercker-select-repository.png
|
||||
|
||||
## Select the repository owner
|
||||
|
||||
@@ -157,7 +157,7 @@ In the next step, Wercker asks you to select the repository owner. Just select y
|
||||
|
||||
![][8]
|
||||
|
||||
[8]: /img/tutorials/wercker-select-owner.png
|
||||
[8]: /img/tutorials/automated-deployments/wercker-select-owner.png
|
||||
|
||||
## Configure access
|
||||
|
||||
@@ -165,7 +165,7 @@ This step can be slightly tricky. As Wercker doesn't access to check out your pr
|
||||
|
||||
![][9]
|
||||
|
||||
[9]: /img/tutorials/wercker-access.png
|
||||
[9]: /img/tutorials/automated-deployments/wercker-access.png
|
||||
|
||||
## Wercker.yml
|
||||
|
||||
@@ -173,7 +173,7 @@ Wercker will now attempt to create an initial *wercker.yml* file for you. Or rat
|
||||
|
||||
![][10]
|
||||
|
||||
[10]: /img/tutorials/werckeryml.png
|
||||
[10]: /img/tutorials/automated-deployments/werckeryml.png
|
||||
|
||||
## Public or not
|
||||
|
||||
@@ -181,7 +181,7 @@ This is a personal choice, you can make an app public so that everyone can see m
|
||||
|
||||
![][11]
|
||||
|
||||
[11]: /img/tutorials/public-or-not.png
|
||||
[11]: /img/tutorials/automated-deployments/public-or-not.png
|
||||
|
||||
## And we've got an app
|
||||
|
||||
@@ -189,7 +189,7 @@ The application is added now, and Wercker will be offering you the chance to tri
|
||||
|
||||
![][12]
|
||||
|
||||
[12]: /img/tutorials/and-we-ve-got-an-app.png
|
||||
[12]: /img/tutorials/automated-deployments/and-we-ve-got-an-app.png
|
||||
|
||||
## Adding steps
|
||||
|
||||
@@ -197,7 +197,7 @@ And now we're going to add the steps themselves. First, we go to the "Registry"
|
||||
|
||||
![][13]
|
||||
|
||||
[13]: /img/tutorials/wercker-search.png
|
||||
[13]: /img/tutorials/automated-deployments/wercker-search.png
|
||||
|
||||
## Using Hugo-Build
|
||||
|
||||
@@ -226,7 +226,7 @@ Once completed a nice tick should have appeared in front of your first build, an
|
||||
|
||||
![][14]
|
||||
|
||||
[14]: /img/tutorials/using-hugo-build.png
|
||||
[14]: /img/tutorials/automated-deployments/using-hugo-build.png
|
||||
|
||||
## Adding a GitHub Pages step
|
||||
|
||||
@@ -258,7 +258,7 @@ And lastly, you can see here that this has a **$GIT_TOKEN** variable. This is us
|
||||
|
||||
![][15]
|
||||
|
||||
[15]: /img/tutorials/adding-a-github-pages-step.png
|
||||
[15]: /img/tutorials/automated-deployments/adding-a-github-pages-step.png
|
||||
|
||||
## Configure the deploy step
|
||||
|
||||
@@ -266,7 +266,7 @@ Simply fill in the name, and make sure you enable **auto deploy** from the **mas
|
||||
|
||||
![][16]
|
||||
|
||||
[16]: /img/tutorials/configure-the-deploy-step.png
|
||||
[16]: /img/tutorials/automated-deployments/configure-the-deploy-step.png
|
||||
|
||||
## Conclusion
|
||||
|
||||
|
||||
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
Reference in new issue
Block a user