Jon Christopher

<p>Template Map is a utility plugin designed to make the creation and management of navigation elements in your custom theme that much easier. It abstracts the need to hard code post IDs and the like from your global and header navigation systems (if you choose to not use Menus) for instance.</p>
<h4>For Example</h4>
<p>Many times you may use something like the following to build your main site navigation:</p>
<pre><code><nav>
  <ul>
    <li>
      <a href="<?php echo get_permalink( 83 ); ?>">About</a>
    </li>
  </ul>
</nav>
</code></pre>
<p>That works great during initial development, and continues to hold up when you migrate to production en masse for the first time. But what about when you’re making subsequent updates and the post IDs in your development environment are different than those in production? You could take the time to sync the databases each and every time, but that’s a bit overkill. Here’s where Template Map comes in to play:</p>
<pre><code><nav>
  <ul>
    <li>
      <?php $about_page_id = TemplateMap()->get_id_from_template( 'template-about.php' ); ?>
      <a href="<?php echo get_permalink( $about_page_id ); ?>">About</a>
    </li>
  </ul>
</nav>
</code></pre>
<p>Template Map allows you to <em>dynamically</em> retreive your desired post ID based on the Page Template you told it to use. Page Template filenames rarely (if ever) change, so it’s the core concept of Template Map’s implementation. Everything works backwards from here.</p>
<p>Naturally this philosophy assumes your Page Template is used only once, it’s important to keep that in mind. Modern client sites often use unique Page Templates for the ‘parent’ pages of each site section.</p>
<h4>Current Site Section</h4>
<p>Template Map also makes it easier to determine whether the current page is within a site ‘section’ which is defined as a top level Page with a unique Page Template that has any number of child Pages and/or Custom Post Types within it. This is very useful when trying to set a ‘current’ state in your navigation, for example:</p>
<pre><code><nav>
  <ul>
    <li class="<?php if( TemplateMap()->maybe_in_section( 'template-about.php' ) ) : ?> current<?php endif; ?>">
      <?php $about_page_id = TemplateMap()->get_id_from_template( 'template-about.php' ); ?>
      <a href="<?php echo get_permalink( $about_page_id ); ?>">About</a>
    </li>
  </ul>
</nav>
</code></pre>
<p>Based on the same principle you can use this utility method to properly orient yourself when outputting conditional classes contingent on the current page being within a ‘secton’ on your site.</p>


Template Map

Automagic mapping of Page Templates to post IDs to facilitate better dynamic link generation

envato

<p>A Template Kit is a collection of pre-designed starter templates for a WordPress Site Builder that share a cohesive visual style.</p>
<p>You can use this plugin to export Template Kits for Elementor.</p>
<p>Once this plugin is activated go to the new “Template Kits” menu to begin creating and exporting your Template Kit.</p>


Template Kit – Export


For some reason TKE does not accept a certain plugin as a dependency when generating an Envato Template Kit despite the fact that the subject plugin IS normally available in the WP plugins repo. Mentioned the problem in the official support forum but no one in charge provided any reasonable explanation.


Quite a bad experience

Use this plugin to export Template Kits for WordPress.

Template Map vs Template Kit – Export