So, I have a dropdown menu on my blog page and I wanted to have the title of the menu be the link to the current page.  I'm using a standard bootstrap3 dropdown for the menu.  Since this is a Drupal 8 site, drupal thankfully adds a class of is-active to the active a tag.  The following code is chunked out:

<div class="dropdown blog-topic-menu">
    <button class="btn btn-default dropdown-toggle blog-topic-title underline" type="button" id="dropdownMenu1" data-toggle="dropdown" aria-haspopup="true" aria-expanded="true">
        &nbsp;
    </button>
    <ul class="dropdown-menu" aria-labelledby="dropdownMenu1">
        <li class="blog-topic-menu-item first-item" title="All Posts">
            <a href="/blog" data-drupal-link-system-path="blog"><i class="fas fa-fw fa-list"></i> All Posts</a>
        </li>
 
        <li class="blog-topic-menu-item" title="Life">
            <a href="/blog/life" data-drupal-link-system-path="blog/life" class="is-active"><i class="fas fa-fw fa-user"></i> Life</a>
        </li>
 
        <li class="blog-topic-menu-item" title="Frosty">
            <a href="/blog/frosty" data-drupal-link-system-path="blog/frosty"><i class="fas fa-fw fa-cat-space"></i> Frosty</a>
        </li>
 
        [...]
 
     </ul>
</div>

$('.dropdown BUTTON.blog-topic-title').html($('.dropdown a.is-active').html() + ' <span class="caret"></span>');

When you go to /blog/life, the menu title is replaced by "Life".

Cross-posted from Stack Exchange.

So, I’m doing some delayed maintenance on this site.  You know, removing modules I don’t need anymore, cleaning up taxonomy, etc, etc.  Technical debt on this site because you know what they say about cobbler’s children and shoes.  When I decide it’s time I’ll be move the site to D9, I want to make the transition smooth.  The site has been around a while.  It was originally a Drupal 4.7 site which has been upgraded to 5, 6, 7 is currently a D8 site.  

So enough preamble, back in the site’s D5 days I had 4 Drupal sites  that I merged into this site.  Since there wasn’t a MigrateAPI 12 years ago, I renumbered the NIDs inside the source sites and then copied the database records into the target site.  In case I needed to debug things, I left gaps between each of the site’s modes (I added 2000 to the NIDs from siteA, 4000 to the NIDs from siteB, etc) so I could easily tell where the nodes came from.  

This is worked and the merged site has been chugging along for over a decade.  I’ve come o a point where the system has ~3,000 nodes but the highest NID is approaching 11,000.  I don’t see any risk here, I’ve worked on much larger sites.  I’m in no danger of exceeding the max number of NIDs anytime soon. 

My question is, Is there any benefit to compressing the NIDs (probably by migration to fresh Drupal installation)?  I don’t see one, but I might be missing something that someone else can see.

As I was rebuilding this site, I added a neat design element that when you click the logo you get a modal box with links not just to home, but the top level of each of my landing pages (my resume, my Drupal consulting services,  my photography services and my blog).  The only downside to this approach was that when javascript is disabled there's no way back to the homepage of the site, 

I know I could use the noscript tag to display the logo linking back to the home page, but how do I hide the code with the javascipty goodness? Simply put I could set display:none on the elements that I wanted to hide in css and enable them in javascript.

See the Pen HTML visible only when Javascript is Enabled. by seanreiser (@seanreiser) on CodePen.