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 Import Template kits for Elementor.</p>
<p>Once this plugin is activated go to “Tools” > “Template Kit” to begin importing.</p>


Template Kit – Import


Removing the Envato Elements plugin is an unbelievably bad decision. For years, it was a key tool that made work faster and smoother, and now they simply killed it. They say it’s because of “new AI tools,” but for real users this feels like a downgrade, not progress.



The new Template Kit Import plugin is a poor substitute, it’s clunky, limited, and definitely not on the same level as the original Envato Elements plugin. What’s worse, many subscribers paid for Envato exactly because of the streamlined workflow the plugin offered. Now it’s gone, and what’s left feels like Envato is walking straight toward its own decline.



This is a shortsighted, almost absurd decision that hurts loyal users more than it helps anyone. I genuinely see this as the beginning of Envato’s downfall if they continue down this path.


Honestly, I can’t believe Envato made this move

Use this plugin to import Template Kits to WordPress

Template Map vs Template Kit – Import