feat: add fileglancer

src/content/projects/fileglancer.md

@@ -0,0 +1,102 @@
+---
+title: Fileglancer
+tagline: "Browse, share, and publish OME-Zarr data."
+maintainer: Allison Truhlar
+#project type - Required. Pick one of the three options - delete the other two.
+project type: [Other]
+#OSSI project status - Required if your project is OSSI-funded. Pick one option.
+# OSSI project status: [Proposed, Accepted, Active Development, Maintenance]
+# OSSI proposal link: Required if your project is OSSI-funded. Preferred - upload the proposal as a PDF to `public/proposals` and provide the link in the format `../../proposals/PROPOSAL.pdf`. Other option - URL to the externally hosted proposal.
+github link: https://github.com/JaneliaSciComp/fileglancer
+documentation link: https://fileglancer-docs.janelia.org
+installation instructions link: https://github.com/JaneliaSciComp/fileglancer#installation
+# preferred contact method: "Creates the link for the 'Reach out for help' button on the project page. Encouraged if there is a preferred way for users to reach out for help other than creating an issue in the project's GitHub repo. Examples: link to Image.sc forum, or an email in the format of mailto:email@example.com."
+# how to cite text: "If your software doesn't have an associated published paper or DOI, delete or comment-out this field to use your GitHub repo as the default. Otherwise, provide the citation for your software - wrap in quotes to ensure colons are interpreted correctly. "
+# how to cite link: "https://doi.org/example - wrap entire link in quotes. If a DOI is not available, then delete or comment-out this field to use your GitHub repo as the default."
+# additional links array:
+#   [
+#     Optional additional external links,
+#     For example - to a project hompage,
+#     External blog posts,
+#     Additional related publications,
+#     Etc.,
+#   ]
+# additional links text array:
+#   [
+#     Optional. The display text you wish to appear for each link provided above,
+#     Display text for link 2,
+#     Display text for link 3,
+#     Display text for link 4,
+#     Etc.,
+#   ]
+image file: ./fileglancer.png
+image caption: Screenshot of the Fileglancer landing page
+# youtube url: https://optional-youtube-url.com
+# youtube caption: Required if you provide a youtube url
+# youtube params: "Optional. Supports any YouTube params: https://developers.google.com/youtube/player_parameters#Parameters. See Astro Embed documentation for more guidance: https://astro-embed.netlify.app/components/youtube/#params"
+#Optional "tag" fields. Select tags from the provided options - delete the options that are not applicable. If you feel another option is required to describe your project, add it and then note this in your pull request.
+development team:
+  [
+    "Scientific Computing Software",
+  ]
+programming language:
+  [
+    "Python",
+    "Javascript",
+    "Typescript",
+  ]
+open source license:
+  [
+    "BSD-3 Clause",
+  ]
+software type:
+  [
+    "Command line application",
+    "Package",
+    "Web application",
+  ]
+use case:
+  [
+    # "Annotation",
+    # "Calcium imaging",
+    # "Confocal light microscopy (LM)",
+    # "Connectomics",
+    # "Correlative light EM (CLEM)",
+    # "Data service",
+    # "Electron microscopy (EM)",
+    # "Electrophysiology",
+    # "Expansion microscopy (ExM)",
+    # "Fluorescence microscopy",
+    # "Image registration",
+    # "Lightsheet fluorescence microscopy (LFSM)",
+    # "Modelling",
+    # "Neural recording",
+    # "Segmentation",
+    # "Sequence analysis",
+    # "Single-molecule localization microscopy (SMLM)",
+    # "Spatial transcriptomics",
+    # "Tool packaging/distribution",
+    # "Tracking",
+    "Visualization",
+  ]
+usage environment:
+  [
+    "HPC cluster",
+    "Local installation",
+    "Web browser",
+  ]
+software ecosystem:
+  [
+    "Neuroglancer",
+  ]
+supported file types:
+  [
+    "N5",
+    "OME-Zarr",
+    "ZARR",
+  ]
+---
+
+To use your project's GitHub README as your project's description - delete all text below the triple dash (---) . Note - your GitHub repo must be public for this to work. This option is strongly encouraged - it will minimize the effort required on your part to keep your software information up to date on this site.
+
+If you wish to provide an alternative description, you can write it here. Separate each paragraph with a blank line. If desired, use [Markdown syntax](https://www.markdownguide.org/basic-syntax/) to add hyperlinks, layout/text effects (e.g., headings, lists, **bold** or _italic_ text), etc.