@paulsterling.bsky.social
I don’t think it’s lost its spark—it’s just changed. From what I’ve seen over the last ~3 years, the energy moved from online to in-person events, which are still fantastic. The fall of Twitter played a role, LinkedIn feels default now(??), and we can’t ignore HQ changes.
November 4, 2025 at 1:20 AM
I don’t think it’s lost its spark—it’s just changed. From what I’ve seen over the last ~3 years, the energy moved from online to in-person events, which are still fantastic. The fall of Twitter played a role, LinkedIn feels default now(??), and we can’t ignore HQ changes.
Wow...impressive!
August 12, 2025 at 6:23 PM
Wow...impressive!
100% agree! So much so that in 2023 we moved our 11 "site" project into single sites and are much better for it. Using #Umbraco Cloud Baselines makes keeping the site's schema in sync pretty easy.
June 23, 2025 at 6:44 PM
100% agree! So much so that in 2023 we moved our 11 "site" project into single sites and are much better for it. Using #Umbraco Cloud Baselines makes keeping the site's schema in sync pretty easy.
Gutted to be missing this year's MVP Summit and #Codegarden ... hope it's a great week for all attending!
June 16, 2025 at 3:43 PM
Gutted to be missing this year's MVP Summit and #Codegarden ... hope it's a great week for all attending!
Remarketing zucks!
May 26, 2025 at 12:15 AM
Remarketing zucks!
@blazorise.bsky.social Any plans for a TimeZone property? If not I assume we'd handle outside the component and then set the correct DateOnly and TimeOnly? An example would be welcome!
May 20, 2025 at 3:14 PM
@blazorise.bsky.social Any plans for a TimeZone property? If not I assume we'd handle outside the component and then set the correct DateOnly and TimeOnly? An example would be welcome!
Excellent! With this we can finally drop the last of the non-Blazorise components.
May 20, 2025 at 2:28 PM
Excellent! With this we can finally drop the last of the non-Blazorise components.