opentofu/website/layouts/downloads.erb

<% wrap_layout :inner do %>
  <% content_for :sidebar do %>
    <h4><a href="/downloads.html">Downloads</a></h4>

    <ul class="nav docs-sidenav">
      <li<%= sidebar_current("downloads-terraform") %>>
        <a href="/downloads.html">Download Terraform</a>
      </li>

      <li<%= sidebar_current("docs-cli-install-apt") %>>
        <a href="/docs/cli/install/apt.html">Debian/Ubuntu APT Packages</a>
      </li>

      <li<%= sidebar_current("docs-cli-install-yum") %>>
        <a href="/docs/cli/install/yum.html">RHEL/Fedora Yum Packages</a>
      </li>

      <li<%= sidebar_current("upgrade-guides") %>>
        <a href="/upgrade-guides/index.html">Upgrade Guides</a>
      </li>
    </ul>

    <%= partial("layouts/otherdocs", :locals => { :skip => "Download Terraform" }) %>
  <% end %>

  <%= yield %>
<% end %>
website: initial commit 2014-07-16 16:51:48 -05:00			`<% wrap_layout :inner do %>`
Update basic scaffolding 2017-04-05 10:28:34 -05:00			`<% content_for :sidebar do %>`
website: Reorganize nav sidebars to improve jumps between sections 2018-12-20 20:18:13 -06:00			`<h4><a href="/downloads.html">Downloads</a></h4>`

Update basic scaffolding 2017-04-05 10:28:34 -05:00			`<ul class="nav docs-sidenav">`
			`<li<%= sidebar_current("downloads-terraform") %>>`
			`<a href="/downloads.html">Download Terraform</a>`
			`</li>`
website: v0.7 Upgrade Guide 2016-08-01 14:37:43 -05:00
website: Initial docs about the APT/Yum repositories The HashiCorp engineering services team has set up APT and Yum repositories as alternative installation methods for various HashiCorp products, now including Terraform. We don't really have a great place to talk about these in our current website structure. There is a longer-term plan to revamp the downloads page to include other options, but we are already getting lots of questions about how to use these repositories and so my goal here is to publish at least a first pass of documentation, linked from the Downloads page sidebar as a placeholder for now, so we'll have somewhere to refer to when answering such questions. My intent is that even once we have a revamped Downloads page that mentions these options more clearly, we'll still need to link out to another page to talk about various details, and so the two new URLs this creates would be the home of that content, even if we rewrite the specific prose here to work better in the context of the new Downloads page. 2020-11-10 18:00:07 -06:00			`<li<%= sidebar_current("docs-cli-install-apt") %>>`
			`<a href="/docs/cli/install/apt.html">Debian/Ubuntu APT Packages</a>`
			`</li>`

			`<li<%= sidebar_current("docs-cli-install-yum") %>>`
			`<a href="/docs/cli/install/yum.html">RHEL/Fedora Yum Packages</a>`
			`</li>`

Update basic scaffolding 2017-04-05 10:28:34 -05:00			`<li<%= sidebar_current("upgrade-guides") %>>`
			`<a href="/upgrade-guides/index.html">Upgrade Guides</a>`
website: Reorganize nav sidebars to improve jumps between sections 2018-12-20 20:18:13 -06:00			`</li>`
			`</ul>`

website: Use a middleman partial for "other docs" list instead of hardcoding it This relies on a commit in the terraform-website repo, and should make updating that list much less annoying. 2019-03-08 05:58:58 -06:00			`<%= partial("layouts/otherdocs", :locals => { :skip => "Download Terraform" }) %>`
Update basic scaffolding 2017-04-05 10:28:34 -05:00			`<% end %>`
website: initial commit 2014-07-16 16:51:48 -05:00
Update basic scaffolding 2017-04-05 10:28:34 -05:00			`<%= yield %>`
			`<% end %>`