| exampleSite/content/blog/migrate-from-jekyll.md | ●●●●● patch | view | raw | blame | history | |
| exampleSite/content/docs/clarity/customize.md | ●●●●● patch | view | raw | blame | history | |
| exampleSite/content/docs/compose/use-tina-cms.md | ●●●●● patch | view | raw | blame | history |
exampleSite/content/blog/migrate-from-jekyll.md
@@ -51,7 +51,7 @@ As a single reference data point, converting my templates for [heyitsalex.net](http://heyitsalex.net/) took me no more than a few hours. ## Convert Jekyll plugins to Hugo shortcodes Jekyll has [plugins](http://jekyllrb.com/docs/plugins/); Hugo has [shortcodes](/doc/shortcodes/). It's fairly trivial to do a port. Jekyll has [plugins](http://jekyllrb.com/docs/plugins/); Hugo has [shortcodes](/docs/compose/shortcodes/). It's fairly trivial to do a port. ### Implementation As an example, I was using a custom [`image_tag`](https://github.com/alexandre-normand/alexandre-normand/blob/74bb12036a71334fdb7dba84e073382fc06908ec/_plugins/image_tag.rb) plugin to generate figures with caption when running Jekyll. As I read about shortcodes, I found Hugo had a nice built-in shortcode that does exactly the same thing. exampleSite/content/docs/clarity/customize.md
@@ -115,7 +115,7 @@ * **menu's languages list** are semi-hardcoded. You may chose another text for the menu entry with [languageMenuName](./exampleSite/config.toml). Please, do better and create a PR for that. * **content** must be translated individually. Read the [official documentation](https://gohugo.io/content-management/multilingual/#translate-your-content) for information on how to do it. **note:** if you do NOT want any translations (thus removing the translations menu entry), then you must not have any translations. **Note:** if you do NOT want any translations (thus removing the translations menu entry), then you must not have any translations. In the exampleSite that's as easy as removing the extra translations from the `config/_default/...` or executing this onliner: ```shell exampleSite/content/docs/compose/use-tina-cms.md
@@ -4,13 +4,13 @@ weight = 3 +++ Do you prefer managing your site using a CMS? Or would you like to make it easier for someone (a non-techie, perhaps) in your team to make edits easily? If interested, follow along. Else, skip to the [next section](../overview/) Do you prefer managing your site using a CMS? Or would you like to make it easier for someone (a non-techie, perhaps) in your team to make edits easily? If interested, follow along. Else, skip to the [next section](../organize-content/) Let's sync your site with Tina CMS. ## Prerequisites !! Obviously you ought to have __a github account__. This is where your website source will live. Basically, Tina will read from github and write (commmit) to your github repo. Obviously you ought to have __a github account__. This is where your website source will live. Basically, Tina will read from github and write (commit) to your github repo. {{< tip "warning" >}} Gitlab or bitbucket will work too. Just check their [implementation here](https://Tina.io/docs/git-sync/gitlab/). Happy fishing. @@ -24,14 +24,14 @@ If you intend to host with something other than Netlify _e.g github pages_, please scroll on. Hosting with Netlify is a lot of fun though; I highly recommend it. ### Step 1 : Fork or Clone Compse theme ### Step 1 : Fork or Clone Compose theme First we will fork [this theme's](https://github.com/onweru/compose) template. ### Step 2 : Add your repository in Tina CMS {{< tip >}} The exampleSite already comes with prefilled placeholdr Tina settings. If you set up your site using [option 2](../getting-started/#option-2-recommended) The exampleSite already comes with prefilled placeholder Tina settings. If you set up your site using [option 2](../install-theme/#option-2-recommended) {{< /tip >}}