How Should a Data Visualisation Developer in Spain Combine Observable, Tableau, and GitHub?
A data visualisation developer should create one portfolio entry per finished analysis or interactive, choose the strongest viewable destination, and describe the question, data source, interaction, and personal contribution.
Observable can explain the notebook, Tableau can show a dashboard, GitHub can expose code, and a live site can present the final experience. Linking all four without context makes the reviewer reconstruct the project, so the portfolio must decide which artifact comes first.
What does each visualisation entry need?
Each entry needs the question answered, the kind of data used, the interaction or format, your role, current status, and one primary proof link.
Name the project in terms a reader understands, not only the library or chart type. The description can mention whether you handled analysis, design, front-end implementation, data preparation, or the complete piece.
Use a metric only for a supported public result. Dataset size or audience figures are not automatically useful; leave the field empty when the meaningful proof is the work itself.
What is the fast way to assemble the visualisation portfolio with IndieShow?
The fast way is to add each visualisation as an IndieShow project, use its tag for the format or stack, and order projects by relevance and current state.
Upload an authorised logo or project image, write a compact description, and use the card's single URL for the best public experience. The dashboard's live preview helps you check whether the first projects make sense without opening every destination.
Place unfinished interactives in Building or Working on, finished pieces in Shipped or Built, and broken or superseded experiments in Archived instead of leaving dead demos among current work.
Build your IndieShow pageClaim your handle, organise the evidence in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.
Should the card link to Observable, Tableau, GitHub, or the live demo?
Link to the destination that lets the intended reviewer understand the finished work with the least setup.
Choose the live demo or public dashboard when interaction is the main evidence, Observable when the explanatory notebook matters, and GitHub when implementation is the key proof and the repository is documented.
Do not duplicate one visualisation into several cards just to expose every URL. Put secondary links inside the primary destination when you control it, or mention their availability in the project description.
How do you handle private or fragile datasets?
Describe the source category and transformation at a safe level, publish only licensed or authorised data, and keep a stable explanatory destination when a live feed can fail.
A public visualisation should not expose client rows or imply that you own a dataset you cannot redistribute. If you created a synthetic demo, label it as synthetic.
For work whose host has disappeared, move the entry to Archived and link an approved write-up if one remains. A dead dashboard is not stronger evidence than an honest archived description.
Related IndieShow guides: combining demos and repositories · showing several projects on one page
Why use IndieShow as the visualisation index?
IndieShow works as the index because it gives every visualisation a consistent status, description, tag, image, optional metric, and destination while preserving one personal URL.
The external platform can then do what it does best: run the notebook, dashboard, repository, or live experience. IndieShow supplies the missing overview across all of them.
Review the page from mobile and while signed out, update outdated links, and let your IndieShow profile remain the single entry point shared in applications or client messages.
Frequently asked questions
What does each visualisation entry need?
Each entry needs the question answered, the kind of data used, the interaction or format, your role, current status, and one primary proof link.
What is the fast way to assemble the visualisation portfolio with IndieShow?
The fast way is to add each visualisation as an IndieShow project, use its tag for the format or stack, and order projects by relevance and current state.
Should the card link to Observable, Tableau, GitHub, or the live demo?
Link to the destination that lets the intended reviewer understand the finished work with the least setup.
How do you handle private or fragile datasets?
Describe the source category and transformation at a safe level, publish only licensed or authorised data, and keep a stable explanatory destination when a live feed can fail.
Why use IndieShow as the visualisation index?
IndieShow works as the index because it gives every visualisation a consistent status, description, tag, image, optional metric, and destination while preserving one personal URL.