wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114broken-link-checker domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114wp-extended-search domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114Luglio 06, 2020
Welcome to our second podcast episode! In this episode we continue our conversation with Nextcloud designer, Jan-Christoph Borchardt, and turn our attention towards design. What is design and how do we handle design at Nextcloud? How to collaborate and what tools to use?
Jan answers these questions and many more, discussing the process of deciding on design changes and community building, accessibility, language support, and usability testing. But Jan also walks through what a new app developer can do to build an app for Nextcloud and how the interaction with them and the wider community and designers goes. Community events, where and how people get together to code and design Nextcloud, release planning – this podcast is 50 minutes and covers almost everything!
Find the feed on our podcast page. If you have not heard the first episode, you can find it there as well.
Enjoy, and leave us feedback below!
Today, we’ll be delving into the fascinating world of app design and exploring how the design team collaborates with the community to create amazing apps. To help us navigate this topic, I am joined by Nimisha Vijay, one of our talented designers at Nextcloud. Shownotes
Per saperne di più
Nextcloud had a busy year to say the least. From events like the Nextcloud Conference to the Nextcloud Hub 3 release and more, 2022 holds many milestones and experiences for our users. In this exciting new episode, Marius talked with Frank about a variety of Nextcloud topics.
Per saperne di piùIn this 16th episode, our host Ingo talked with Daphne Muller, the Support lead at Nextcloud. Daphne shared with us the interesting story that led her to Nextcloud, her well-known Tedx talk on privacy and much more!
Per saperne di più
