DalavanCloud

<?php
/**
 * Below you will find all of the custom content used to
 * create the demo site for the Dynamik Promote Skin.
 */
?>

WordPress Menu Setup: Assign a menu to the "Primary Navigation Menu" as well as the Genesis "Header Right" Widget Area as stated below.

== BEGIN Widget Area Info ==

DalavanCloud

<?php
/**
 * Below you will find all of the custom content used to
 * create the demo site for the Dynamik Vitality Skin.
 */
?>

WordPress Menu Setup: Assign a menu to the "Primary Navigation Menu".

== BEGIN Widget Area Info ==

DalavanCloud

<?php
/**
 * Below you will find all of the custom content used to
 * create the demo site for the Dynamik RealEstate Skin.
 */
?>

WordPress Menu Setup: Assign a menu to the "Primary Navigation Menu" as well as the Genesis "Header Right" Widget Area as stated below.

== BEGIN Widget Area Info ==

DalavanCloud

<?php
/**
 * Below you will find all of the custom content used to
 * create the demo site for the Dynamik ThemeShop Skin.
 */
?>

WordPress Menu Setup: Assign a menu to the "Primary Navigation Menu" as well as the "Secondary Navigation Menu".

== BEGIN Widget Area Info ==

DalavanCloud

<?php
/**
 * Below you will find all of the custom content used to
 * create the demo site for the Dynamik NonProfit Skin.
 */
?>

WordPress Menu Setup: Assign a menu to the "Primary Navigation Menu" as well as the Genesis "Header Right" Widget Area as stated below.

== BEGIN Widget Area Info ==

DalavanCloud

<?php
/**
 * Below you will find all of the custom content used to
 * create the demo site for the Dynamik Parallax Skin.
 */
?>

WordPress Menu Setup: Assign a menu to the "Primary Navigation Menu" as well as the Genesis "Header Right" Widget Area as stated below.

== BEGIN Widget Area Info ==

DalavanCloud

<?php
/**
 * Below you will find all of the custom content used to
 * create the demo site for the Dynamik Impact Skin.
 */
?>

WordPress Menu Setup: Assign a menu to the "Primary Navigation Menu".

== BEGIN Widget Area Info ==

DalavanCloud

function custom_extender_pro_not_labeled() {

	if ( is_singular() && get_post_meta( get_the_ID(), '_extender_pro_' . extender_pro_sanitize_string( extender_pro_active_theme_name(), true ) . '_labels', true ) == '' )
		return true;
	else
		return false;
	
}

DalavanCloud

Dynamic module loading done right

Follow-up to Top-level await is a footgun – maybe read that first

Here are some things I believe to be true:

1. Static module syntax is beneficial in lots of ways – code is easier to write (you get better linting etc) and easier to optimise (tree-shaking and other things that are only really possible with static syntax), and most importantly, faster to load (it's trivial for a module loader to load multiple dependencies concurrently when they're declared with a static syntax – not so with imperative statements like require(...) or await import(...)).
2. App startup time is perhaps when performance is most critical. (You already know this, I don't need to cite the studies.)
3. If you're in favour of constructs that jeopardise app startup time, you are anti-user. Top-level await is such a construct.

DalavanCloud

Top-level await is a footgun 👣🔫

Follow-ups:

• Why imperative imports are slower than declarative imports
• Dynamic module loading done right
• Non-deterministic module ordering is an even bigger footgun

As the creator of Rollup I often get cc'd on discussions about JavaScript modules and their semantics. Recently I've found myself in various conversations about top-level await.