Jeff DePascale

As a dedicated fan of PoolSuite FM, I've taken matters into my own hands. With no Android version available, I'm leveraging NativeScript to create my own. Follow my journey through this tutorial series and witness the progress firsthand! #PoolSuiteFM #AppDevelopment #NativeScript #Vuejs #AndroidDevelopment #WeekendProject

1

The two possible syntaxes for CSS masonry have been merged into one draft specification. It's a lot to get through, so we wrote a post explaining the differences between creating a masonry layout with display: masonry and with display: grid. Take a look, and if you have an opinion one way or the other, let us know! #css https://lnkd.in/eTnJBWuZ

48

1 Comment

Design-to-Dev handover is historically riddled with confusion — especially for accessibility. Watching the Grammarly design team use Stark to make their product accessible is so exciting (especially as users*). *Yes, we use Grammarly to fix Stark.

39

2 Comments

So... DocBook is officially dead? 💀 In all seriousness, does this matter? Curious what people think. I think this is also a good moment to draw a fundamental contrast between DITA and DocBook. Because DocBook is a predefined and rigid vocabulary that is controlled by the TC, no longer having a TC is pretty significant, I think. DITA on the other hand, is a standard whose foundation is a set of principles rather than tags. So, while DITA still has a working TC, even if it didn't, people could continue to evolve the functional tag set without one. https://lnkd.in/eyjGpk8d

20

5 Comments

Heydon Pickering provides the lowdown on the <aside> element and how it should be used. https://buff.ly/4dVuA7E #HTML #Semantics #WebDev #WebDevelopment #DigitalAccessibility #Accessibility #A11y

4

Based on a preliminary try out of #Drupal CMS, I opine that it's not easy enough for those who just want a place to post cat pics. I propose instead working with hosting providers and cPanel: https://lnkd.in/eJfHzsx3

6

3 Comments

LVN re-renders quickly and you'll have a functioning interactive native application that coordinates with a server in less that 5 minutes. Let’s see somebody beat that! 📝 https://loom.ly/wmCZZkA #MyElixirStatus #ProductDevelopment

9

Steve Faulkner visits WCAG success criterion 1.4.3: Contrast (Minimum) and shares his view that it sucks as while the control is disabled for all, only for a subset of users (low vision) the text label for the disabled control is illegible. https://buff.ly/4hAMWx1 #UXDesign #WebDev #WebDevelopment #DigitalAccessibility #Accessibility #A11y

6

1 Comment

Your "Epic" 100-Node Automation is Actually a Red Flag 🚩 Stop celebrating spaghetti automations. If you're proud of your massive n8n, Make, or Zapier workflow, we need to talk. That complex automation you just posted? The one getting all the LinkedIn likes? It's a ticking time bomb of technical debt that your team will eventually have to defuse—with interest. I've spent years cleaning up these mega-workflows, and here's what I've learned: The best automation builders think like API architects, not workflow hoarders. Here's the better way: Transform your massive workflows into modular "internal APIs": - Break workflows at webhook triggers (your new "API endpoints") - Each sub-workflow becomes a reusable service - Clean input/output contracts between modules - Works in n8n, Make, Zapier, or anywhere with webhook support This approach delivers real results: 1. Maintainability: Each "endpoint" has one job—debug in minutes, not hours 2. Reusability: Call your "endpoints" from any workflow—true automation DRY principles 3. Scalability: New team members will thank you (instead of cursing your name) Your automation is working when you see: - Workflows under 30 nodes - Reusable components across projects - Clear documentation through structure - Happy team members who can actually maintain your work 🎯 Ready to fix this? Look at your largest automation. Find processes that could be their own "endpoints." If you'd make it a separate API endpoint in traditional development, make it a separate workflow in your automation platform. Complex workflows impress LinkedIn. Clean infrastructure impresses teams.

315

115 Comments

Glide just publicly released workflows yesterday. I think a lot of people don't even realize how powerful that now makes Glide. Here's just one example. Have you played with Workflows yet? What are your thoughts?

60

6 Comments

You've been there - stuck in some app, desperately clicking that “HELP” button, only to be met with either a terrible search box or a frustrating AI-powered chat bubble that offers little to no help. The truth is, users getting lost or confused is a big reason why they disengage. That’s why we’ve upgraded Appcues Launchpads to deliver help exactly when and where your users need it. Noticeable and (actually) useful without being annoying. Whether it’s a tour, a link, or a help doc, Launchpads offers self-support that’s perfectly timed, perfectly themed, and perfectly helpful. No engineering required. No annoying “ping” sounds. Just a smoother experience for your users. ps: I'm really proud of the team that brought this to life, specifically Joseph Muething, Alexandre S. and Magdiel Duarte. (But don't poach them. I need them.)

12

The Microsoft 365 Copilot announcements yesterday included two great new capabilities available with Copilot Studio: 1) Copilot agents built in Copilot Studio can now be published directly into Microsoft 365 Copilot, surfacing right in the user’s flow of work and 2) a new Copilot Studio experience will empower users of any skill level to create Copilot agents from within SharePoint and Microsoft 365 Copilot Business Chat (BizChat). Read more in the blog from Charles Lamanna: https://lnkd.in/ef565q4y #CopilotStudio #MSPartner #PowerPlatform #Blog

29

The new release of SpotterStudio.com is here, with a bunch of exciting enhancements!! ❇  BRAINSTORM: New "mini package" functionality in the ideation side panel ❇  BRAINSTORM: Collapsible sections in the the ideation side panel ❇  CALENDAR: New creative calendar view for projects ❇  PROJECTS: New top-level "Published | In Progress" filter ❇  PROJECTS: Default state for new projects is now "Team" instead of "Private" ❇  PROJECT DETAIL: New video types ❇  FEATURE GUIDES: In-app contextual video guides for Outliers, Projects and Brainstorming, from our creator-in-residence Peter Hollens 🟣 ❇  Visual and functionality fixes and improvements #YouTube #Creator #Spotter

61

2 Comments

How HTML elements are supported by screen readers, a Work in progress by Steve Faulkner https://buff.ly/3w0CyM3 #HTML #ScreenReaders #ScreenReader #WebDev #WebDeveloper #Accessibility #A11y

25

1 Comment

Google is onto something big with NotebookLM (I wish the name of the app was better, but I digress). I provided my blog/website URL and asked for an "audio summary", which created the recording below (a simulated podcast-style audio of two robots talking about me). But before you go follow that link, let me say I see it as an amazing summarization/learning tool. Just feed content in one format (say, Internet articles on Japanese cooking) and get a conversational summary in podcast form to listen during your daily commute.

21

4 Comments

Understanding CSR and SSR - Tech 101 for PMs! 🌐 When we visit a website, there are two main ways it can show us information: Client Side Rendering (CSR) and Server Side Rendering (SSR). :: Client Side Rendering (CSR) :: Client Side Rendering (CSR) means that most of the work happens in your web browser. The browser gets a small piece of information from the server and then builds the whole page right there. Think of CSR like making a sandwich at home. You get all the ingredients from the store, and then you put them together yourself. ➡️ CSR in action: If you visit Instagram on your phone, you might see the layout before photos fully appear—this is CSR in action! Advantages of CSR [1] Feels fast and smooth once everything is loaded [2] Great for websites that look like apps and need user interaction Disadvantages of CSR [1] Takes longer to load at first and can be slow on weaker connections [2] Crawling bots may find it difficult to crawl the website :: Server Side Rendering (SSR) :: Server Side Rendering (SSR) is when the server does most of the work. The server prepares the entire webpage and sends it to your browser all at once. Think of SSR like ordering a sandwich from a restaurant. You place your order, and they make it for you before serving it at your table. ➡️ SSR in action: When you search on Google, the results load quickly and show up all at once. Advantages of SSR [1] Faster initial load time [2] Good for SEO - crawlers can easily read the information Disadvantages of SSR [1] Pages might feel slower when you start clicking around [2] Needs more server power to handle each request In simple terms, CSR is like building the page on your device, while SSR sends you the completed page right away. Liked this? Repost and share with your network. #Technology #ProductManagers

68

7 Comments

“People are still using FileMaker?" I heard this question recently and thought it deserved a proper answer. The short version? Absolutely yes, take healthcare IT as an example. FileMaker isn't just surviving; it's thriving. Here's why: - Rapid Development: FileMaker allows for quick creation of custom apps, crucial in the fast-paced healthcare environment. - Flexibility: It easily integrates with other systems, a must for modern healthcare IT ecosystems. - User-Friendly: Its intuitive interface means less training time for busy healthcare professionals. - Scalability: FileMaker grows with your organization, from small clinics to large hospital systems. Don't just take my word for it. Here are some real-world examples: - LuminFire developed TrackUS, a HIPAA-compliant mobile healthcare app using FileMaker, featuring encryption, secure data transmission, and role-based security for protecting patient information. - Lee Medical implemented FileMaker Go on iPads to reduce hospital infections, improving patient care through efficient data management and actionable insights. - Numerous Federally Qualified Health Centers and Community Health Centers use FileMaker-based solutions to manage patient data securely while ensuring HIPAA compliance. These industry leaders choose FileMaker for its robust capabilities and ease of customization. At Harmonic Data, we've seen through firsthand experience how FileMaker continues to revolutionize healthcare IT operations. From streamlining patient intake to managing complex research data, FileMaker remains a powerful tool in the industry. What's your experience with FileMaker in healthcare? Have you encountered any misconceptions about its relevance? #HealthcareIT #FileMaker #HarmonicData #DataManagement

8