Jonathan, Steve, and I were all on the meeting. We started out and jumped into some general world building concepts. Just trying to keep Jonathan in the loop and seeing where we are going or where new development is happening. After that, we turned the presentation over to him and he showed us what he has been working on. Still lots of mapping, gathering, and what not. We have him on a big project - cleaning out the garage and helping us to organize things... :)

Here are some notes from the day:

- 3 main navigation buttons or area that people want to be in - they are where do you want to go? What do you want to do? How can I show you or let you pull the reports you want? In a nutshell - go, do, reports

- The Go section would be broken down into different navigation type or screens. We were thinking of cards with icons, a zoomed in map, the core layout (radial fan), and a build your own section. The Do section would be somewhat a mini search engine built into the system. They user would type a word and we would bring back results for them to click on. For example: they type discount and we show different discounts options, reports, help files, videos, etc. Super simple search with built-in navigation. The other section would be the reports or what you want to see (show me) section. We spent quite a bit of time on this section, but the main gist was categories, sub reports under those categories, and settings to allow for the page to be customized and organized as needed.

- Going back to the zoomed out map idea with icons. Jonathan took the existing interactive map, added some icons and simplified the design a bit. Great starting point.

- The action or do section could be setup like a mini google area or search engine within the system. Make it fun and light but able to jump to assets that deal with the task at hand.

- 3 different type of tools - Tools for entering data, tools for searching data, and tools for showing the results of the searches (reports).

- Lots of talk about settings. What different types of settings are there? World level (corporation wide settings), Industry specific settings, main 12 player group settings, page level settings, and individual user settings.

- Splitting up the settings into the different player groups and even allowing for page level drill-downs as needed. For example: Say we were dealing with settings for invoices. We have all of those and we also show all pages inside the invoice section that also have settings. Be able to do all different kinds of settings from one spot (corp-wide, group level, page level, and user settings).

- We got into lots of talks and discussions about build your own navigation systems. Be able to set icons, colors, naming convention, sort order, tool tips, custom URL or pick from a list, and other individual button/nab type settings.

- It would be super cool if you could turn things on/off and then drag and drop into a placeholder or a grid of sorts

- As we were talking about custom built navigation systems, I started to think about the my cart favorite buttons. We allow general buttons, photo buttons, nested or group buttons (be able to stack things), colors, custom names, add/edit custom categories (ways of organizing and grouping like buttons), custom sort options, copy or use other user's buttons, etc. Lots of fun ideas. Instead of just POS (point of sale) buttons, be able to do something similar for custom navigation. Anyways, use my cart favorite buttons or that idea to build out custom navigation systems. This could be a cool addition for the fracture stuff.

- Going along with the custom navigation buttons, we may also want to allow for colors, icons, categories, custom sort options, special placement options, etc. Turn it into a virtual pallet of sorts (pull and organize your space like an artist using a pallet for a painting). Super flexible.

- The term cohesiveness came out a number of times. Making the site cohesive through tools, apps, pages, sites, products, and even marketing.

- As a company matures, it often tries to use a designed system approach. This included style guides, requirements, code snippents, cascading CSS, components, and style assets that could be used over and over again (one to many relationship between a component and what it does and/or looks like or functions like).

Great meeting and fun conversation. Towards the end, Steve was encouraging Jonathan to keep dreaming and refining as we go. We are trying to catch the over all vision. As we keep going, we may even need to circle back around and see how the new ideas could relate to the rest of the system. Trying to get to that cohesive type design level. See attached for some screenshots.