From 304cf8b6b2b6769200d6964e6869cbed086fd52f Mon Sep 17 00:00:00 2001 From: Serghei Iakovlev Date: Sun, 17 Jul 2022 20:50:13 +0200 Subject: Format external links for demo site --- exampleSite/content/about.md | 10 +++++----- exampleSite/content/contact.md | 5 ++--- exampleSite/content/credits.md | 21 ++++++++++---------- exampleSite/content/documentation/index.md | 32 +++++++++++++++--------------- exampleSite/content/thanks.md | 2 +- 5 files changed, 34 insertions(+), 36 deletions(-) (limited to 'exampleSite') diff --git a/exampleSite/content/about.md b/exampleSite/content/about.md index 4ca2f94..2f28cab 100644 --- a/exampleSite/content/about.md +++ b/exampleSite/content/about.md @@ -23,17 +23,17 @@ useful type of editions for editors and readers. An edition produced with Ed con pages whose rate of decay is substantially lower than database-driven systems. As an added bonus, these static pages require less bandwidth. Our hope is that our approach can help beginners and veterans deploy beautiful editions with less effort, and that it can help us teach a 'full stack' -[in one academic semester](https://github.com/susannalles/MinimalEditions/blob/master/README.md), +{{< link src="https://github.com/susannalles/MinimalEditions/blob/master/README.md" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}in one academic semester{{< /link >}}, while allowing us to care for our projects at less cost, and perhaps, just perhaps, to generate high-quality editions on github.io in large quantities based on the -[git-lit](http://jonreeve.com/2015/09/introducing-git-lit/) model by Jonathan Reeve. We're coming +{{< link src="http://jonreeve.com/2015/09/introducing-git-lit/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}git-lit{{< /link >}} model by Jonathan Reeve. We're coming for you, Kindle! - ## Sample Ed editions. -- [Our sample site](https://gohugo-theme-ed.netlify.app/) is the first edition built with Ed. -- [Serghei Iakovlev's blog](https://serghei.blog/?utm_source=ed&utm_campaign=docs&utm_medium=smm) + +- [Our sample site]({{< ref "/" >}}) is the first edition built with Ed. +- {{< link src="https://serghei.blog/?utm_source=ed&utm_campaign=docs&utm_medium=smm" class="external" target="_blank" hreflang="ru" rel="noopener noreferrer" >}}Serghei Iakovlev's blog{{< /link >}} ## Current Features diff --git a/exampleSite/content/contact.md b/exampleSite/content/contact.md index d46c277..79b6e30 100644 --- a/exampleSite/content/contact.md +++ b/exampleSite/content/contact.md @@ -6,11 +6,10 @@ semanticType: contact This is an example of a custom shortcode that you can put right into your content. You will need to add a form action to the the shortcode to make it work. -Check out [Formspark](https://formspark.io/) for a simple, free form service. +Check out {{< link src="https://formspark.io/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Formspark{{< /link >}} for a simple, free form service. Ed theme is not strictly tied to any forms backend. You can easily use any backend -like [Formspark](https://formspark.io/), [Formspree](https://formspree.io/), -[FabForm](https://fabform.io) and so on just by changing the `formAction` parameter +like {{< link src="https://formspark.io/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Formspark{{< /link >}}, {{< link src="https://formspree.io/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Formspree{{< /link >}}, {{< link src="https://fabform.io/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}FabForm{{< /link >}} and so on just by changing the `formAction` parameter in the site configuration file. For a more subtle configuration of the contact form itself, you can also replace diff --git a/exampleSite/content/credits.md b/exampleSite/content/credits.md index bb86f05..e81e056 100644 --- a/exampleSite/content/credits.md +++ b/exampleSite/content/credits.md @@ -2,35 +2,34 @@ title: Credits --- -### [Serghei Iakovlev](https://www.linkedin.com/in/egrep/) | Software Engineer +### {{< link src="https://www.linkedin.com/in/egrep/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Serghei Iakovlev{{< /link >}} | Software Engineer -Serghei Iakovlev is a software engineer with 20 years of experience in IT who enjoys finding elegant solutions to non-trivial problems. Serghei focused on the goal and driven by visual sophistication and laser-sharp precision, he take pride in every finished project, and never stop learning along the way. Seghei work as the Head Of Development with 20 teams of 90+ engineers to develop [airSlate](https://airslate.com) --- better nocode workflow automation platform. +Serghei Iakovlev is a software engineer with 20 years of experience in IT who enjoys finding elegant solutions to non-trivial problems. Serghei focused on the goal and driven by visual sophistication and laser-sharp precision, he take pride in every finished project, and never stop learning along the way. Seghei work as the Head Of Development with 20 teams of 90+ engineers to develop {{< link src="https://airslate.com" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}airSlate{{< /link >}} --- better nocode workflow automation platform. -### [Susanna Allés Torrent](http://susannalles.github.io/) | Hyper philologist +### {{< link src="http://susannalles.github.io/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Susanna Allés Torrent{{< /link >}} | Hyper philologist Susanna teaches Digital Humanities in the Department of Latin American and Iberian Cultures. She earned her Ph.D in Romance Studies at the University of Barcelona in 2012, and completed a M.A. in «Nouvelles technologies appliquées à l’histoire» at the École Nationale des Chartes (Paris). She has taught at the University of Barcelona and she has been a postdoctoral fellow at the Spanish National Research Council (CSIC). Her research explores several aspects of digital humanities, especially, scholarly digital editions, electronic text analysis, intertextuality and text reuse, and digital lexicography. She also works with the intersection of the Iberian Peninsula and Italy in the Middle Ages and the Renaissance, reconstructing cultural and literary networks between the two. - -### [Terry Catapano](https://github.com/tcatapano) | Metadata ninja +### {{< link src="https://github.com/tcatapano" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Terry Catapano{{< /link >}} | Metadata ninja Terry Catapano is a Librarian in Columbia University Libraries' Digital Program Division. He was Chair of the Society of American Archivists' Schema Development Team, responsible for the development of Encoded Archival Description version 3, and is a member of the ArchivesSpace Technical Advisory Group and the Editorial Board for the Metadata Encoding and Transmission Standard (METS). As Vice President of Plazi Verein, he leads the development of the TaxPub extension of the National Library of Medicine/National Center for Biotechnology Information Journal Publishing DTD, and has worked on digitizing, text mining, and providing open access to the literature of biological systematics, including collaborations with WikiData, the Encylopedia of Life, the Global Biodiversity Information Facility (GBIF), ZooBank, and CERN. -### [Alex Gil](http://www.elotroalex.com/) | Resident minimalist +### {{< link src="http://www.elotroalex.com/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Alex Gil{{< /link >}} | Resident minimalist -Alex is the Digital Scholarship Coordinator for the Humanities and History at Columbia University. He is vice chair of the [Global Outlook::Digital Humanities](http://www.globaloutlookdh.org/) initiative focusing on minimal computing and translation, is one of the founders and directors of [Columbia's Group for Experimental Methods in the Humanities](http://xpmethod.plaintext.in/) and the [Studio@Butler](https://studio.cul.columbia.edu/), and is actively engaged in several digital humanities projects at Columbia and around the world. +Alex is the Digital Scholarship Coordinator for the Humanities and History at Columbia University. He is vice chair of the {{< link src="http://www.globaloutlookdh.org/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Global Outlook::Digital Humanities{{< /link >}} initiative focusing on minimal computing and translation, is one of the founders and directors of {{< link src="https://xpmethod.columbia.edu/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Columbia's Group for Experimental Methods in the Humanities{{< /link >}} and the {{< link src="https://studio.cul.columbia.edu/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Studio@Butler{{< /link >}}, and is actively engaged in several digital humanities projects at Columbia and around the world. -### [Johann Gillium](https://github.com/JohannGillium) | Search master +### {{< link src="https://github.com/JohannGillium" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Johann Gillium{{< /link >}} | Search master -After having studied digital humanities at the Ecole nationale des Chartes in Paris, Johann has worked in France as a librarian at the Bibliothèque interuniversaire de Santé, where he most notably contributed to the [Vesalius project](http://www3.biusante.parisdescartes.fr/vesale/debut.htm), the digital edition of several works by the great anatomist Andreas Vesalius. +After having studied digital humanities at the Ecole nationale des Chartes in Paris, Johann has worked in France as a librarian at the Bibliothèque interuniversaire de Santé, where he most notably contributed to the {{< link src="https://www3.biusante.parisdescartes.fr/vesale/debut.htm" class="external" target="_blank" hreflang="fr" rel="noopener noreferrer" >}}Vesalius project{{< /link >}}, the digital edition of several works by the great anatomist Andreas Vesalius. --- ## Acknowledgments -As many open source projects, Ed is the work of community. The project starts with the open web, and everything in between leading to [Hugo](https://gohugo.io/) and the wonderful team who wrangled that Go in our favor. This theme is adopted and finalized with new functionality from [Jekyll](https://jekyllrb.com/) [Ed](https://github.com/minicomp/ed) theme by [Alex Gil](https://twitter.com/elotroalex). The original Ed theme stylesheets are built on top of [Lanyon](https://github.com/poole/lanyon), a Jekyll theme based on [Poole](http://getpoole.com), "the Jekyll butler," both created by [Mark Otto](https://github.com/mdo) and distributed with an MIT license. Thanks, Mark, for your helpful streamlining! Special hat tips to brother-in-markdown-arms, [Chris Forster](https://github.com/c-forster), and the generous [Sylvester Keil](https://github.com/inukshuk/) for his work on Jekyll Scholar. +As many open source projects, Ed is the work of community. The project starts with the open web, and everything in between leading to {{< link src="https://gohugo.io/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Hugo{{< /link >}} and the wonderful team who wrangled that Go in our favor. This theme is adopted and finalized with new functionality from {{< link src="https://jekyllrb.com/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Jekyll{{< /link >}} {{< link src="https://github.com/minicomp/ed" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Ed{{< /link >}} theme by {{< link src="https://twitter.com/elotroalex" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Alex Gil{{< /link >}}. The original Ed theme stylesheets are built on top of {{< link src="https://github.com/poole/lanyon" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Lanyon{{< /link >}}, a Jekyll theme based on {{< link src="https://getpoole.com/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Poole{{< /link >}}, "the Jekyll butler," both created by {{< link src="https://github.com/mdo" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Mark Otto{{< /link >}} and distributed with an MIT license. Thanks, Mark, for your helpful streamlining! Special hat tips to brother-in-markdown-arms, {{< link src="https://github.com/c-forster" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Chris Forster{{< /link >}}, and the generous {{< link src="https://github.com/inukshuk/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Sylvester Keil{{< /link >}} for his work on Jekyll Scholar. -We are strongly indebted to the research work and conversations stemming out of our [Columbia's Group for Experimental Methods in the Humanities](http://xpmethod.plaintext.in/)—or as we like to call it: \#xpmethod; the wonderful international comradery of [GO::DH](http://www.globaloutlookdh.org/); and of course, the support of our [Columbia University Libraries](http://library.columbia.edu/) and its cozy [Studio@Butler](https://studio.cul.columbia.edu/). +We are strongly indebted to the research work and conversations stemming out of our {{< link src="https://xpmethod.columbia.edu/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Columbia's Group for Experimental Methods in the Humanities{{< /link >}}—or as we like to call it: \#xpmethod; the wonderful international comradery of {{< link src="http://www.globaloutlookdh.org/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}GO::DH{{< /link >}}; and of course, the support of our {{< link src="https://library.columbia.edu/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Columbia University Libraries{{< /link >}} and its cozy {{< link src="https://studio.cul.columbia.edu/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Studio@Butler{{< /link >}}. ...and to the writers that inspire us to scribble notes on the margins we protect with our work. Thank you. diff --git a/exampleSite/content/documentation/index.md b/exampleSite/content/documentation/index.md index 8797571..a504bdb 100644 --- a/exampleSite/content/documentation/index.md +++ b/exampleSite/content/documentation/index.md @@ -12,27 +12,27 @@ featuredImage: screenshot-home.png This documentation was built with beginners in mind, but has the necessary information for more seasoned producers. -To install and use Ed you will be using your terminal. If you need a refresher, I highly recommend "[The Command Line Crash Course](https://www.computervillage.org/articles/CommandLine.pdf)." Working knowledge of HTML and CSS is also taken for granted. If you're new to HTML and CSS, you may want to check out the relevant courses on [codecademy.com](https://www.codecademy.com/learn/web). +To install and use Ed you will be using your terminal. If you need a refresher, I highly recommend "{{< link src="https://www.computervillage.org/articles/CommandLine.pdf" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}The Command Line Crash Course{{< /link >}}". Working knowledge of HTML and CSS is also taken for granted. If you're new to HTML and CSS, you may want to check out the relevant courses on {{< link src="https://www.codecademy.com/learn/web" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}codecademy.com{{< /link >}}. --- ## Installing Ed -Before starting, please be sure that you have [installed Hugo](https://gohugo.io/getting-started/quick-start/#step-1-install-hugo) and [created a new site](https://gohugo.io/getting-started/quick-start/#step-2-create-a-new-site). After that, you are ready to install Ed. +Before starting, please be sure that you have {{< link src="https://gohugo.io/getting-started/quick-start/#step-1-install-hugo" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}installed Hugo{{< /link >}} and {{< link src="https://gohugo.io/getting-started/quick-start/#step-2-create-a-new-site" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}created a new site{{< /link >}}. After that, you are ready to install Ed. -Please note, to install Ed, you must have [Go >= 1.12](https://golang.org/dl/) installed on your computer. You probably have Go already, but if you don't, the easiest way is probably to install is to follow [Go installation instruction](https://go.dev/doc/install). To check if Go is running on your system enter the following line on your terminal (remember to ignore the `$`): +Please note, to install Ed, you must have {{< link src="https://golang.org/dl/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Go >= 1.12{{< /link >}} installed on your computer. You probably have Go already, but if you don't, the easiest way is probably to install is to follow {{< link src="https://go.dev/doc/install" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Go installation instruction{{< /link >}}. To check if Go is running on your system enter the following line on your terminal (remember to ignore the `$`): ~~~ bash $ go version ~~~ -If you don't get an error, you're good to go. Using the `cd` command on your terminal, navigate to the folder where you keep your web projects. Once you're in the folder where project live, initialize the [Hugo Modules](https://gohugo.io/hugo-modules) system using the following line (replace `` and `` by real names): +If you don't get an error, you're good to go. Using the `cd` command on your terminal, navigate to the folder where you keep your web projects. Once you're in the folder where project live, initialize the {{< link src="https://gohugo.io/hugo-modules" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Hugo Modules{{< /link >}} system using the following line (replace `` and `` by real names): ~~~ bash $ hugo mod init github.com// ~~~ -Take a look inside the [`exampleSite`](https://github.com/sergeyklay/gohugo-theme-ed/tree/master/exampleSite) folder of this theme. You'll find a folder called [`config`](https://github.com/sergeyklay/gohugo-theme-ed/blob/master/exampleSite/config). Copy the [`config`](https://github.com/sergeyklay/gohugo-theme-ed/blob/master/exampleSite/config) folder in the project root of your Hugo site. Check the contents of the `config` folder and configure it. +Take a look inside the `{{< link src="https://github.com/sergeyklay/gohugo-theme-ed/tree/master/exampleSite" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}exampleSite{{< /link >}}` folder of this theme. You'll find a folder called `{{< link src="https://github.com/sergeyklay/gohugo-theme-ed/blob/master/exampleSite/config" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}config{{< /link >}}`. Copy the `config` folder in the project root of your Hugo site. Check the contents of the `config` folder and configure it. After that, import the theme adding the following lines to `config/_default/config.yaml`: @@ -70,11 +70,11 @@ Copy the url from your terminal log and paste it into your browser of choice. Th ## Hugo -Ed is a Hugo theme. That means you will need some familiarity with Hugo to take advantage of its full potential. While running a Hugo site is a bit more involved than Wordpress and other similar tools, the payoff in the long term is worth the effort to learn it. If you are new to Hugo, I recommend you take a look at [A Guide to Using Hugo](https://strapi.io/blog/guide-to-using-hugo-site-generator) at *Strapi*, [Host on GitHub](https://gohugo.io/hosting-and-deployment/hosting-on-github/) on *Hugo Documentation Site* and [Hugo's own documentation](https://gohugo.io/documentation/) to start getting a sense of how it works. +Ed is a Hugo theme. That means you will need some familiarity with Hugo to take advantage of its full potential. While running a Hugo site is a bit more involved than Wordpress and other similar tools, the payoff in the long term is worth the effort to learn it. If you are new to Hugo, I recommend you take a look at {{< link src="https://strapi.io/blog/guide-to-using-hugo-site-generator" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}A Guide to Using Hugo{{< /link >}} at *Strapi*, {{< link src="https://gohugo.io/hosting-and-deployment/hosting-on-github/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Host on GitHub{{< /link >}} on *Hugo Documentation Site* and {{< link src="https://gohugo.io/documentation/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Hugo's own documentation{{< /link >}} to start getting a sense of how it works. -Once you have gone through these tutorials, you can get started using Ed. Remember to always and only edit content files for your site using [a plain text editor](https://en.wikipedia.org/wiki/Text_editor), and *not* a word processor. I'm composing this file using a plain text editor called [Visual Studio Code](https://code.visualstudio.com/). +Once you have gone through these tutorials, you can get started using Ed. Remember to always and only edit content files for your site using {{< link src="https://en.wikipedia.org/wiki/Text_editor" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}a plain text editor{{< /link >}}, and *not* a word processor. I'm composing this file using a plain text editor called {{< link src="https://code.visualstudio.com/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Visual Studio Code{{< /link >}}. -You should make sure that all your texts have the YAML [Front Matter](https://gohugo.io/content-management/front-matter/) (the information at the top of the file). YAML stands for "YAML Ain't Markup Language" --- no disrespect to XML --- and it's the main way that Hugo handles named data. Here's an example of YAML Front Matter: +You should make sure that all your texts have the YAML {{< link src="https://gohugo.io/content-management/front-matter/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Front Matter{{< /link >}} (the information at the top of the file). YAML stands for "YAML Ain't Markup Language" --- no disrespect to XML --- and it's the main way that Hugo handles named data. Here's an example of YAML Front Matter: ~~~ yaml --- @@ -100,15 +100,15 @@ featuredImage: screenshot-home.png # Featured image of the text --- ~~~ -For more information about all available standard front matter variables, please read [Hugo Front Matter](https://gohugo.io/content-management/front-matter/). +For more information about all available standard front matter variables, please read {{< link src="https://gohugo.io/content-management/front-matter/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Hugo Front Matter{{< /link >}}. --- ## Markdown and CommonMark -Ed is designed for scholars and amateur editors who want to produce either a clean reading edition or a scholarly annotated edition of a text. The main language we use to write in the Hugo environment is called Markdown. To learn more about the Markdown family, see Dennis Tenen and Grant Wythoff's "[Sustainable Authorship in Plain Text using Pandoc and Markdown](http://programminghistorian.org/lessons/sustainable-authorship-in-plain-text-using-pandoc-and-markdown)." +Ed is designed for scholars and amateur editors who want to produce either a clean reading edition or a scholarly annotated edition of a text. The main language we use to write in the Hugo environment is called Markdown. To learn more about the Markdown family, see Dennis Tenen and Grant Wythoff's "{{< link src="http://programminghistorian.org/en/lessons/sustainable-authorship-in-plain-text-using-pandoc-and-markdown" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Sustainable Authorship in Plain Text using Pandoc and Markdown{{< /link >}}". -By default Hugo uses a special Markdown processor called Goldmark. The processor can be said to use it's own 'flavor' of Markdown called CommonMark, and sometimes the Markdown syntax will be different than other flavors of Markdown. CommonMark is a rationalized version of Markdown syntax with a spec whose goal is to remove the ambiguities and inconsistency surrounding the original Markdown specification. It offers a standardized specification that defines the common syntax of the language along with a suite of comprehensive tests to validate Markdown implementations against this specification. You can become familiar with the CommonMark syntax in the [CommonMark documentation](https://spec.commonmark.org/). Another way to become familiar is to examine the sample text source files we provided. +By default Hugo uses a special Markdown processor called Goldmark. The processor can be said to use it's own 'flavor' of Markdown called CommonMark, and sometimes the Markdown syntax will be different than other flavors of Markdown. CommonMark is a rationalized version of Markdown syntax with a spec whose goal is to remove the ambiguities and inconsistency surrounding the original Markdown specification. It offers a standardized specification that defines the common syntax of the language along with a suite of comprehensive tests to validate Markdown implementations against this specification. You can become familiar with the CommonMark syntax in the {{< link src="https://spec.commonmark.org/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}CommonMark documentation{{< /link >}}. Another way to become familiar is to examine the sample text source files we provided. --- @@ -245,15 +245,15 @@ The `{.poetry}` tag at the end tells the processor to think of the lines above i ## Pages -Your editions are treated as [sections](https://gohugo.io/content-management/sections/) or [page bundles](https://gohugo.io/content-management/page-bundles/) in Ed. Other web pages in your site exist outside the `content` folder. Default homepage, for example, is constructed from the `index.html` file found on the `layouts` folder of Ed theme. +Your editions are treated as {{< link src="https://gohugo.io/content-management/sections/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}sections{{< /link >}} or {{< link src="https://gohugo.io/content-management/page-bundles/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}page bundles{{< /link >}} in Ed. Other web pages in your site exist outside the `content` folder. Default homepage, for example, is constructed from the `index.html` file found on the `layouts` folder of Ed theme. -You will notice that the homepage in particular has a `.html` file ending instead of a `.md` ending. All template files in Hugo are HTML, and the index behaves as a template file. Although these files are mostly written in HTML, notice that they may contain [template tags](https://gohugo.io/templates/introduction/). To create your own homepage create `index.html` file in project `layouts` folder, making sure that your changes to `index.html` are written in valid HTML. The same goes for all Ed's template files in the `layouts` folder. +You will notice that the homepage in particular has a `.html` file ending instead of a `.md` ending. All template files in Hugo are HTML, and the index behaves as a template file. Although these files are mostly written in HTML, notice that they may contain {{< link src="https://gohugo.io/templates/introduction/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}template tags{{< /link >}}. To create your own homepage create `index.html` file in project `layouts` folder, making sure that your changes to `index.html` are written in valid HTML. The same goes for all Ed's template files in the `layouts` folder. --- ## Tables of Content -You will find three kinds of Tables of Content in Ed. The first example is in the list of Latest Publications in the Homepage. This list is generated using the [templating language](https://gohugo.io/templates/introduction/). This is one of the major components of Hugo, and I recommend you deepen your knowledge of it if you want to modify the logic that automates much of Ed. Here is the code that generates the Latest Publications list on the homepage: +You will find three kinds of Tables of Content in Ed. The first example is in the list of Latest Publications in the Homepage. This list is generated using the {{< link src="https://gohugo.io/templates/introduction/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}templating language{{< /link >}}. This is one of the major components of Hugo, and I recommend you deepen your knowledge of it if you want to modify the logic that automates much of Ed. Here is the code that generates the Latest Publications list on the homepage: ~~~ html
@@ -272,7 +272,7 @@ To override this list, create file `mini-toc.html` inside `layouts/partials` fol As you can see, the templating tags `{{ }}` are embedded into the HTML. These tags often use programmatic logic, as is the case here. However, another use of these tags is pull data from your project. In the example above it pulls the `Title` from each allowed post type. -As you may have noticed already, we are basically adapting the blogging features of Hugo to our own ends, what Cuban designer and theorist Ernesto Oroza would call "[technological dissobedience](http://www.ernestooroza.com/)." +As you may have noticed already, we are basically adapting the blogging features of Hugo to our own ends, what Cuban designer and theorist Ernesto Oroza would call "{{< link src="https://www.ernestooroza.com/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}technological dissobedience{{< /link >}}". The second kind of table of content is exemplified in this documentation. If you open the source file for the documentation, you will notice at the top this snippet: @@ -296,7 +296,7 @@ The internal links pointing to the right sections in your document are generated ## Getting help -That should do it. If you have suggestions on how to improve Ed, make sure to leave us a line on [our issues page](https://github.com/sergeyklay/gohugo-theme-ed/issues), or send us a pull request. If you run into an issue that isn't answered by this documentation or the [`exampleSite`](https://github.com/sergeyklay/gohugo-theme-ed/tree/master/exampleSite), then visit the [Hugo forum](https://discourse.gohugo.io/). The folks there are helpful and friendly. **Before** asking your question, be sure to read the [requesting help guidelines](https://discourse.gohugo.io/t/requesting-help/9132). Feel free to tag me in your question, my forum username is [@egrep](https://discourse.gohugo.io/u/egrep/summary). +That should do it. If you have suggestions on how to improve Ed, make sure to leave us a line on {{< link src="https://github.com/sergeyklay/gohugo-theme-ed/issues" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}our issues page{{< /link >}}, or send us a pull request. If you run into an issue that isn't answered by this documentation or the `{{< link src="https://github.com/sergeyklay/gohugo-theme-ed/tree/master/exampleSite" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}exampleSite{{< /link >}}`, then visit the {{< link src="https://discourse.gohugo.io/" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}Hugo forum{{< /link >}}. The folks there are helpful and friendly. **Before** asking your question, be sure to read the {{< link src="https://discourse.gohugo.io/t/requesting-help/9132" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}requesting help guidelines{{< /link >}}. Feel free to tag me in your question, my forum username is {{< link src="https://discourse.gohugo.io/u/egrep/summary" class="external" target="_blank" hreflang="en" rel="noopener noreferrer" >}}@egrep{{< /link >}}. Happy editing! diff --git a/exampleSite/content/thanks.md b/exampleSite/content/thanks.md index cf5e6bc..2e5b2ed 100644 --- a/exampleSite/content/thanks.md +++ b/exampleSite/content/thanks.md @@ -6,4 +6,4 @@ private: true Your message will be sent within a short time. We'll answer as soon as possible. -[← Back to Home](/). +[← Back to Home]({{< ref "/" >}}). -- cgit v1.2.3