The development guide is getting out of hand. There is a very long list of pages and it's not even all about development of Dataverse. It's very hard to find things and people probably don't use it a lot, as some information is outdated and - you guessed it - hard to find.
Should we talk about creating a third level of TOC? Split up the pages into more sections like "Develop", "Integrations", "Release Processes" or something along these lines?
Yes, it's in dire need of a rewrite.
As a sanity check, we still like having it as a guide, right? Next to the other guides, I mean. You don't think we should split it off into its own separate world, do you? (It's ok if you do!)
Here's a suggestion. WDYT?
Getting Started
- Introduction
- Development Environment -> "Setup Dev Environment (Docker)"
- Classic Dev Environment -> "Setup Dev Environment (Classic)"
- Windows Development -> "Setup Dev Environment (Windows)"
- Version Control -> "Contribute Your Code" + Page "Version Control Strategy" in Daily Dev
- Security -> "Security Issue Handling"
- Tools
Daily Development
- Coding Style
- Dependency Management
- Debugging
- SQL Upgrade Scripts
- Tips
Architecture and Design
- Consuming Configuration
- API Design
- Performance
- Geospatial Data
- Universal Numerical Fingerprint (UNF)
Testing and Quality
- Testing
- Troubleshooting
- Deployment -> "Deploying Review Environments"
Java Extensions and SPIs
- Search Services
- Metadata Export Formats
Integrations and APIs
- Dataset Migration API
- Dataset Semantic Metadata API
- Globus Transfer API
- Direct DataFile Upload/Replace API
- Make Data Count
- Auxiliary File Support
- Shibboleth, OAuth and OIDC
- Workflows
Release and Pipeline Engineering
- Making Library Releases
- Making Releases
Specialized Topics
- Font Custom
Delete:
Move To Installation Guide:
What a third level can look like: we already have an example by @Philip Durbin π here: https://guides.dataverse.org/en/latest/container/running/index.html
This would mostly only move things around plus a few renames. We can iterate from there, restructuring and adding more documentation.
(And I can start adding docs for the fixture and other testing bits)
Apart from a few quibbles here and there, this looks fantastic! :tada:
Question though: Is the frontend in scope?
The frontend has its own dev guide here: https://github.com/IQSS/dataverse-frontend/blob/develop/DEVELOPER_GUIDE.md
I'd say one day it should be included. I feel like the community appreciates we have 1 place we put all the docs. But it may not be necessary. We certainly would have enough places to put a nice introduction and crosslink to the detailed frontend guide. (e.g. in "Getting started")
I'd say the main guide should at least cover how to spin up the frontend. And possibly how to test from js-dataverse (that's why @Jan Range and I added this recipe). Because often you're creating or updating an API that will be used by these downstream projects.
That sound reasonable. Should we lean more into the "backend" / "frontend" bit in the page titles?
Yeah, that's what I'm thinking.
To acknowledge the new reality.
We could move the classic and windows pages to the "special topics" section, then there's plenty of space for a page "Backend Dev Environment" and "Frontend Dev Environment"
Obviously, we should see what @Ellen K @Cheng Shi and @Juan Pablo Tosca Villanueva think. Plus, @Eryk Kulikowski has hacked on the frontend. And @Vera Clemens has worked on a lot on js-dataverse. I just kicked off #ui-dev > dev guide reorg
What other quibbles do you have?
Geospatial Data seems a bit out of place.
Lots of the APIs should move from the dev guide to the API guide.
Geospatial Data: the page should probably be renamed. It talks about how Dataverse ingests shapefiles, so this kind of is about architecture. But I'm open to suggestions.
Also, and this is frontend-related, we should probably kill the Style Guide while we're at it. Or fold it under the new dev guide org for eventual killing, as part of JSF removal.
I agree with moving API stuff to the API guide, but then I need to reorg the API guide, too :see_no_evil:
Sure, we can do it in chunks.
Yeah, we could move the style guide to a subsection. Might be nice to call it "Legacy Frontend" or something. Or just put it under Specials, together with the Font Custom
@Oliver Bertuch if you really want, you can post something to https://groups.google.com/g/dataverse-dev . It would be the first message of 2026! :sweat_smile:
I have a suspicion no one will give a dime... :see_no_evil: It's not a lot of people caring about docs :zany:
Yes. We do have @Dieuwertje Bloemen @Vaida PlankytΔ π¨ and @AmΓ©lie Fiocca though! The Documentation Working Group! :tada: Just wait until you see our poster! :smile:
Oh, and anything new we write should be in .md rather than .rst
Do we have MyST etc in place?
Oh I see it in requirements.txt
Wait a second. I just found your QA bits. Should we think about re-integrating these things?
The QA Guide? What about it?
I just suggested a section on "Testing and Quality". And there's a section on "Release and Pipeline Engineering". Shouldn't we try to re-add the QA engineering bits into this?
Instead of having two guides this closely related?
I understand it's mostly about the internal processes, but it's still about development.
Honestly, I don't think anyone would care if we delete the QA guide. I don't think anyone looks at it. It was sort of a failed experiment. But maybe we could fold some of its content into the dev guide, like you're saying. ![]()
And I totally get why you put it in a new guide altogether - the current state of the dev guide simply is too crowded and the QA pages would have made things worse
I'd like that!
I just started writing up my bits and bobs about the fixtures etc and am going to add that in a new folder "testing" in the "developers" folder. That way I'm unblocked and can create the content, no need to wait on a reorg. If I do this in a month, I've probably forgotten about it all :see_no_evil:
Sure, that sounds fine.
ah, merging and simplifying documentation, one of the nicer things in life :sunglasses:
@Oliver Bertuch see! @Vaida PlankytΔ π¨ cares about docs! :heart: ![]()
Crazy idea: let's talk about this in Barcelona, maybe even do some hands on editing?
Sure! I could even bring it up during the doc working group meeting in Barcelona if you want: #docs > docs wg at DCM 2026 in Barcelona
Yeah that's what I meant :sweat_smile:
Sry should have been more specific...
Sure, I just added it to the agenda: https://docs.google.com/document/d/1dX8ktajVsRDk-MDF-yHWV0f4vIe8U3DWrSzIerVGlF8/edit?usp=sharing
Heads up to @Dieuwertje Bloemen, my partner in crime. :smile:
Last updated: May 30 2026 at 06:18 UTC