Skip to content

Conversation

@nicopace
Copy link
Contributor

@nicopace nicopace commented Oct 15, 2025

Solves #34.

I used AI for providing general structure to the text I wrote, for concistency.

Copy link
Member

@rudokemper rudokemper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent work, @nicopace!

I have added many copy editing, syntactical, and markdown fixes intended to polish up the document. Please go through these before merging. But the content here is great. Thank you!


Reviewing this, one thing I am thinking about (which I'm sure occurred to you too) is modularity.

We might eventually have a "From KoboToolbox to GC Explorer" guide, where the contents of ## 1. Data Collection: KoboToolbox would be duplicated entirely. Or a "From CoMapeo to Superset", with the same observation about the Superset section. How to organize this? I wonder if there is a clever Docusaurus feature or plugin we can use for this kind of behavior where the same content might be included in multiple pages or sections.

Maybe something we tackle when we do #33, or a future "Visualizing KoboToolbox data in GC Explorer (sub)guide).

@nicopace
Copy link
Contributor Author

Excellent work, @nicopace!

I have added many copy editing, syntactical, and markdown fixes intended to polish up the document. Please go through these before merging. But the content here is great. Thank you!

Reviewing this, one thing I am thinking about (which I'm sure occurred to you too) is modularity.

We might eventually have a "From KoboToolbox to GC Explorer" guide, where the contents of ## 1. Data Collection: KoboToolbox would be duplicated entirely. Or a "From CoMapeo to Superset", with the same observation about the Superset section. How to organize this? I wonder if there is a clever Docusaurus feature or plugin we can use for this kind of behavior where the same content might be included in multiple pages or sections.

Maybe something we tackle when we do #33, or a future "Visualizing KoboToolbox data in GC Explorer (sub)guide).

Indeed something to think about.

There are functionalities within Docusaurus that we can use to reuse parts of the documentation in other parts, contributing to the maintainability.

I can explore it for the next PR, so we can reuse the content in this one for the next one.

nicopace and others added 2 commits October 21, 2025 12:56
Co-authored-by: Rudo Kemper <31662219+rudokemper@users.noreply.github.com>
@nicopace nicopace merged commit a8b0055 into main Oct 21, 2025
@nicopace nicopace deleted the 34-workflow-kobo-to-superset branch October 21, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[REFERENCE] From KoboToolbox → Windmill → Data Warehouse → GC-Explorer and Superset

3 participants