Add v2 Supported File Formats page; mark existing file-support as v1.26#111
Open
keitawf wants to merge 2 commits into
Open
Add v2 Supported File Formats page; mark existing file-support as v1.26#111keitawf wants to merge 2 commits into
keitawf wants to merge 2 commits into
Conversation
The only file-format documentation on the site described Nanome 1.26 (the "exhaustive list" even included formats v2 dropped, e.g. .ccp4/.dsn6/.nanome). - New docs/nanome_web/fileformats.md: the v2 supported formats (through 2.6.0), adapted from the internal reference — import/export capability per format, trajectory playback, surfaces, limitations, and per-version history. Dropped the internal-only "go-forward rule" and a dead cross-reference. - FAQ: add a "What file formats does Nanome v2 support?" answer linking the new page; tag both existing answers "(v1.26)" with a v2 pointer. - Tag the v1.x format lists (navigating, menus, howto) "(v1.26)" and point to the v2 page. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying nanome-docs with
|
| Latest commit: |
8f851d5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4c6f53d4.nanome-docs.pages.dev |
| Branch Preview URL: | https://v2-5-file-formats.nanome-docs.pages.dev |
- Nanome Web / Loading Structures: note the web app accepts the full range of file types and link the Supported File Formats page. - Main Panel / Entries and Components: clarify that XR loads structures by PDB code from the RCSB, while other file types are loaded from the web app; link both the web loading page and the file formats list. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Heads up: the new v2 file-formats table here inherited a few extensions from the wiki doc that WorkspaceAPI doesn't actually parse (Alex flagged it; verifiable by grepping
Full recognized set (with real aliases): pdb/ent, mmcif/cif, sdf, pdbqt, pqr, mae, moe, pse, xyz, gro, xtc, trr, dcd, dx, fasta(fa/faa/seq), smi/smiles, molz. (The older v1.26 lists are a separate question.) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #110. The only file-format documentation on the site described Nanome 1.26 — the FAQ's "exhaustive list" even included formats v2 dropped (
.ccp4,.dsn6,.psf,.nanome).Changes
docs/nanome_web/fileformats.mdunder Nanome Web: the v2 supported formats through 2.6.0 — per-format import/export capability, trajectory playback, import/export surfaces, limitations, and per-version history. Adapted from the internal reference doc; dropped the internal-only "go-forward rule" and a dead cross-reference to a nonexistent Guidance page.navigating,navigation/menus,howto): tagged the format lists (v1.26) and pointed to the v2 page.Notes
Verification
npm run docs:buildpasses with no dead links. All internal links and anchors validated with a script, including the FAQ deep-link into#trajectory-molecular-dynamics(VitePress validates page paths but not anchors). Previewed on localhost; the new page and both tagged FAQ answers render correctly.🤖 Generated with Claude Code