Best approach for Tableau 'AddOns'? #34
Description
The other day I added Heroicons and DaisyUI to a Tableau site (heex/tailwind).
This required a bit of research. I captured my learning in the form of a PR (#32). The PR was rejected by @mhanberg, noting that there could be potentially many UI libraries, and that it would be better to have a more systematic approach to handle a variety of add-on tools and use-cases.
Here's an initial cut at the potential tools and services that people may want to use with their Tableau site:
| Category | Providers |
|---|---|
| SVG Icons | Heroicons |
| UI Components | DaisyUI, Petal, Mishka Chelekom, SaladUI, FluxonUI, LiveState, Vite |
| Analytics | Google Analytics, Plausible |
| Deployment | Github Pages, Cloudflare, Netlify |
How best to guide Tableau developers? I think there are a few alternative approaches:
- Documentation (Github Wiki, Guides on HexDocs)
- Demo Sites (Hackery, etc.)
- Code Generators (Igniter/Mix Tasks, TableauNew cli options)
IMO the simplest approach would be to add Markdown Guides to elixir-tools/tableau, and expose them on hexdocs.pm.
Then the generated pages/home_page.ex could say "To learn more about Tableau configuration and add-on tools, read the GUIDES"`
@mhanberg LMK if & how you would like to support Tableau 'AddOns'.