cfa-library / citesoftware.org Goto Github PK

• E.g., use a CITATION.cff file and list them in the references

As I learned during the work on #8, this theme in combination with the Jekyll action used in the build and deploy workflow, the baseurl in _config.yml needs to be set to the name of the repository for resolution of relative links to work.

Once we rename this repository, we need to change this as well.

• Diff https://cite.research-software.org with this website to identify gaps / things that should and shouldn't be copied over.
  • This site will go away or redirect
• Also diff https://citation-file-format.github.io
  • This site will stay, but content shouldn't be duplicated

E.g., from institutions beyond those of @danielchivvis, @jspaaks, @sdruskat.

1. Have a look at the current flow & identify gaps/wrong turns
2. Come up with a v0.1
3. Let a UX professional look at the flow to make sure we solve the right problem for the right audience (result: wireframes)

Start basic, then add stuff like

• institutional support/endorsements (see #4)
• governance (see #3)

• E.g., Chrome has Lighthouse (a built-in tool), and there are others (Google Admin Console or similar).
• Use schema.org JSON-LD

This could reflect the decision tree structure for better accessibility.

• E.g., could this be under the wings of the FORCE11 SCIWG?