Common issues and solutions for Willemstad theme users. ## Installation Issues ### Theme Not Appearing After Installation **Symptoms:** Willemstad doesn't show in theme dropdown **Solutions:** 1. Ensure file is named `theme.css` (not `Willemstad.css`) 2. Check file is in `.obsidian/themes/Willemstad` folder 3. Restart Obsidian completely ### Style Settings Options Missing **Symptoms:** No Willemstad options in Style Settings **Solutions:** 1. Install Style Settings plugin if not already installed 2. Enable Style Settings plugin 3. Close and re-open Obsidian ## Appearance Issues ### Colours Look Wrong or Inconsistent **Common Causes:** - Plugin conflicts (Style Settings, in particular) **Solutions:** 1. Disable Style Settings and re-enable it (or delete Style Settings and reinstall) 2. Reset Willemstad to defaults in Style Settings (not recommended, usually the first option works) 3. Check for CSS snippets that override theme colours 4. Ensure that you are not using an Experimental base tone as these are generally wacky ### Interface Elements Invisible or Misplaced **Symptoms:** Missing buttons, weird spacing, overlapping elements **Solutions:** 1. Check ribbon style setting - try reverting to "Default" 2. Reset icon sizes to defaults 3. Disable custom line length overrides ### Fonts Not Displaying Correctly **Symptoms:** Unexpected fonts, missing characters, poor rendering **Solutions:** 1. Use suggested fonts (Inter, DM Sans, Manrope, DM Mono) 2. Reset font settings to Willemstad defaults 3. Check system font availability 4. Clear font cache on Windows/Linux ## Performance Issues ### Obsidian Running Slowly and High Memory Usage **Immediate Fixes:** 1. Enable "No Animations" in Root Options 2. Enable "No Blur Backdrop Filter" 3. Disable floating ribbon if enabled 4. Reduce blur intensity on status bar **Advanced Solutions:** - Limit use of floating callouts in large documents - Use standard callouts instead of complex layouts ## Plugin Compatibility ### Specific Plugin Conflicts **Kanban Plugin:** - Issue: Columns not displaying correctly - Fix: Enable "Fit to Width" options or try vertical scrolling mode **Advanced Tables:** - Issue: Toolbar appears broken - Fix: Enable "Remove Willemstad-Set Toolbar Tweaks" **Templater:** - Issue: Code formatting looks wrong - Fix: Enable "Remove Willemstad-Set Templater Tweaks" **Theme-Related Plugins:** - Disable other theme plugins (Minimal Theme Settings etc.) - Check for CSS snippet conflicts - Review plugin load order ### General Plugin Issues **Symptoms:** Plugins look wrong or don't function **Troubleshooting Steps:** 1. Test with only Willemstad + Style Settings enabled 2. Add plugins back one by one 3. Check plugin-specific Willemstad settings 4. Report compatibility issues on [GitHub](https://github.com/tingmelvin/willemstad-x) ## Platform-Specific Issues ### Windows & Linux **Scrollbar Issues:** - Try "Hide Scrollbars" option in Root Options - Check if system scrollbar settings conflict **Titlebar Problems:** - Ensure "Use Accent Colour for Titlebar" setting matches preference - Try disabling titlebar control buttons ### macOS & iOS, and Mobile Devices(Limited Support) > [!warning] Willemstad has not been tested on Apple platforms **Solutions:** - Report issues on GitHub - Try reverting font settings to system defaults - Use simpler interface configurations ## Content Display Issues ### Callouts Not Working **Symptoms:** Callouts appear as regular text **Solutions:** 1. Check callout syntax: `>[!type]` 2. Ensure Style Settings has callout options enabled 3. Try standard callout types first 4. Test the callouts via the markdown provided in the documentation 5. Check for conflicting CSS snippets ### Tables Displaying Incorrectly **Common Issues:** - Striping not appearing - Colours looking wrong - Alignment problems **Solutions:** 1. Toggle "Disable Table Striping" setting 2. Check table markdown syntax 3. Test with Bases plugin disabled 4. Verify no conflicting table plugins ### Headers Not Coloured **Troubleshooting:** 1. Check "No Coloured Headers" is disabled 2. Verify accent colours are properly set 3. Try resetting header colour settings 4. Check document isn't using CSS classes that override headers ## Frequently Asked Questions ### Q: Can I use Willemstad without Style Settings? **A:** Basic functionality works, but you'll miss 90% of customisation options (especially its colour options). Style Settings is highly recommended. ### Q: Why do some features require specific base lightness settings? **A:** Certain colour schemes (like Solarized, Nord) have specific contrast requirements to ensure its true-to-theme colours are being displayed. The recommendations ensure optimal appearance. ### Q: Can I mix presets from different categories? **A:** Yes, but some combinations may not work well together. Experiment with backups of your settings. ### Q: How do I backup my Willemstad configuration? **A:** Style Settings allows export/import of configurations. Use this before major changes. ### Q: Is Willemstad compatible with Obsidian Publish? **A:** Basic styling works, but advanced features requiring Style Settings won't transfer. Consider simplified configurations for published content. You can obtain a Willemstad for Publish file from this website under `publish.css`. However, this is still under development and will be released on GitHub once finalised. ### Q: Why doesn't mobile support exist? **A:** Mobile interface requirements differ significantly from desktop, limited time and resources means that has not been covered. ### Q: Can I contribute colour schemes or features? **A:** Yes! See the Contributing guide for contribution guidelines. ## Getting Help ### Before Reporting Issues 1. **Test with minimal setup** - Disable other plugins/themes 2. **Check existing issues** - Search GitHub issues first 3. **Include system info** - Obsidian version, OS, plugin list 4. **Provide screenshots** - Visual issues are easier to diagnose ### Where to Get Help **GitHub Issues:** Technical problems and bug reports **Obsidian Discord:** Community discussion and quick questions **Documentation:** Check all relevant guides first ### Information to Include in Bug Reports - Obsidian version - Operating system - List of active plugins - Steps to reproduce issue - Screenshots or recordings - Browser console errors (if applicable) ### Information to Include in Feature Requests - Clear description of desired functionality - Use case explanation - Mockups or examples if relevant - Consideration of existing alternatives