A few+ requests

I’m using Local by Flywheel v2.3.4 after seeing a demo at WordCamp NYC 2018.

While I think Local is a great step in the right direction, there were quite a few discoverability issues. As a proficient developer my initial draw was to find out how to use the WP-CLI. It took a while to search the forums only to find a thread about using right-click. It seems a lot of bullet points in the marketing are things you have to search to learn how to use unfortunately.

Here are a few+ notes on personal prefernce…

  • Defaults

    • Add ability to set default admin name:password
    • Add ability to set default plugins
      • Use tags like fields using slugs from WordPress.org http://api.wordpress.org/plugins/info/1.0/${slug}/
    • Add ability to set default SSL [ true | false ]
    • Add option to check for updates on startup (since this product is evolving)
  • SSL

    • Add option for pre-enable SSL on site creation
      • Note: Permission is granted on site creation anyway, so you should have the ability to trust the cert there.
  • Live Link

    • On hover should show tooltip or have (i)
  • Add-ons

    • In List View, add a link to website or more information for any add-on. Turning on and add-on does not help me understand what the add-on does or how I am supposed to use it later.
  • A discoverable way to tunnel commands to instance.

    • ssh -t user@example.local "sudo command"
  • Tools

    • Include vim out-of-the-box so you have an editor when you ssh into the site.
  • PHP

  • Utilities

    • Include button to open add-ons configuration.
      • Button will open preferences and go to the add-ons tab.
  • Blueprints

    • Include file size next to blueprint
    • Include date created next to blueprint
    • Include button to open blueprint directory (Reveal BluePrints Folder) or next to each item: (Reveal Blueprint in finder)
    • Show a site’s blueprints
      • Note: Currently you have to go to the preferences then blueprints tab. Would be nice to click on a site and see all the blueprints that have been created from it.
  • Per Site Additions

    • Installed Tab (easy to use wp-cli to gather this info)

    • Logs

      • Show button to open debug log (apache error | wp-content/debug.log)
      • Move from [HELP] menu to it’s own [VIEW] menu
      • tail -f to see debug log in app in real-time
  • Configuration

    • Varnish VCL
      • Some documentation of where to find the common logs/configurations.
  • Help

    • Documentation on how to do things
      • Help for any bullet point in the marketing (screenshots would be nice)