https://web.dev/unused-javascript/

Use past tense, remove link to sign up form, link to the category on discourse

The main./README.md and /content/README.md have redundant, but mismatched content. To-Dos need to be cleaned up and/or moved to GitHub Issues.

"See also the analysis of CWL Implementations by the BioExcel Center of Excellence."

https://docs.bioexcel.eu/cwl-engine-guide/about.html#summary-of-engines

To be added below the "Partial Implementations" table

With project and organizational logos; also with pre-CWL major events like Taverna's SCUFL: https://www.slideshare.net/soilandreyes/2011-0706-scufl2-poster-because-a-workflow-is-more-than-its-definition-bosc-2011

Sub headings e.g. https://www.commonwl.org/v1.1/Workflow.html#CommandInputRecordField have wrong font/formatting. Thanks!

When making a PR, we can pre-populate it with a list of checklist of style and content guidelines. e.g.

https://docs.google.com/document/d/1uh18NImnHWCzibpluVpZ7lY2xmwk_VaSxD2-YyXzBQA/edit?usp=sharing

The add-jekyll-site branch needs to parse both _config.yml and _config_staging.yml, in order for the staging site to properly function as a staging site. I didn't want to touch the Jenkins build config, but the respective terminal command would be bundle exec jekyll build --config "_config.yml,_config_staging.yml".

This is largely why #54 (incorrect nav links issue) came up.

@tetron @mr-c

Example: https://www.commonwl.org/v1.2/Workflow.html

https://search.google.com/search-console/mobile-usability/drilldown?resource_id=sc-domain%3Acommonwl.org&item_key=CAw&hl=en-DE&sharing_key=9hp-Lpk2kPlWirr-KJFnGg

@tetron had some changes that he suggested that I thought would be good to incorporate into the draft before we get feedback from the larger group. Maybe @lunacodes can do these?

This is the list, I believe. @tetron can verify :)

• * Convert both the banner and the boxes on the main page to be clickable links (the whole graphic) instead of having it have a blue hyperlink inside. The banner should link to the discourse post about the conference: https://cwl.discourse.group/t/2022-cwl-conference-feb-28-mar-4-2022/519
• * Reorder the gallery entries to put the bioinformatics users first, then the geospatial, hydrology, radio astronomy and general. Basically this is to keep the most compelling stories first
• * Rename Users Gallery to User Gallery
• * Make Features a Single Page -- if it looks too large, we could consider adding a left-nav. Based on what Luna thinks looks best.
• * Move the Background Section from Community to the Features Page. Instead of naming it about - call it "Benefits of Workflows and Standards"
• * Move the list of Contributors to the About section in their own page. I believe this is where we landed Peter, but if this is wrong let me know.
• * Put a maximum width on the text, at least for the text-heavy pages like "Getting Started" or now it would be in Features or About, I believe (added based on Peter's suggestion below)

Additional bug that I added -

• * I can't seem the link to BOSC to work in the timeline, so the hyperlink just needs to be fixed. Sorry about that.

Thanks @lunacodes.

https://www.commonwl.org/cwl-staging/#CWL_Advisors

I noticed with the most recent preview that nav and many other urls are pointing to commonwl.org instead of https://deploy-preview-NUM--cwl-website.netlify.app/

Attempting a fix for it.

Include information on sponsorship tiers.

Example: https://cesium.com/blog/categories/userstories/

All nav links using {{ site.url }}{{ site.baseurl}} are outputting as https://www.commonwl.org/cwl-staging/. Need to adjust _config.yml and _config_local.yml

https://s.apache.org/existing-workflow-systems

name: The ACROSS European Project
logo: https://www.acrossproject.eu/wp/wp-content/uploads/2021/03/ACROSS_Logo_107x28.jpg
website: https://www.acrossproject.eu/
section: Cross-Domain

(via https://github.com/common-workflow-language/common-workflow-language/wiki/Notable-CWL-mentions%2C-adoption%2C-and-users/#the-across-european-project )

"CWL is for dataflow style batch analysis, where the units of processing are command line programs. " On the https://www.commonwl.org/ page if you added that as the second sentence (after "The Common Workflow Language (CWL) is an open standard...") I think that would make it clear. Something similar could go into the spec with more info, though once you get to a spec you usually know why you are there. But maybe a Scope Statement/Section - "What it is" and "What it isn't" (e.g., "explicitly not for business process modeling") would be helpful there to bound change requests.

https://gitter.im/common-workflow-language/common-workflow-language?at=5f96dc6c57fe0a4f30359951

https://gitter.im/common-workflow-language/common-workflow-language?at=5f96099beb82301c1a4c348a

These are minor edits - and do not need to prevent the website from going live, but I just wanted to list them here for @lunacodes.

• For the development tools page:
  ** you probably don't need the extra development tools header. https://deploy-preview-75--cwl-website.netlify.app/tools/
  ** capitalize every description in the unless it is lowercase because of the tool name, e.g. cwltool
• For the implementations page:
  ** Local is sometimes capitalized and sometimes not -- I would personally suggest lowercase
• For the repos page:
  ** Remove any periods after entries so they are all consistent.
• For the projects page:
  ** Capitalize all entries and remove periods
• For the gallery page:
  ** Some of the entries are missing periods at the end.

Most of these were my fault , but if you could help clean them up - that would really be helpful.

These are more suggestions than minor edits to consider:

• Center the logos on the bottom row in the minor users gallery on the main page -- they look a little odd to me justified to the left. No sure if that is just me though.

@lunacodes looks like when I google cwl, cwl workflow or common workflow language - we don't really get hits on the main website - we get mostly links to the standards or the user guide. The standards have a link back to the main page but the user guide doesn't. Any ideas on how to make the website show up better in google searches? Thanks! Also is it possible to make a link back to the main page from the User Guide @tetron ?

Example: https://www.commonwl.org/v1.2/Workflow.html

https://search.google.com/search-console/mobile-usability/drilldown?resource_id=sc-domain%3Acommonwl.org&item_key=CAk&hl=en-DE&sharing_key=TDNaQle_OJJgQK833IaDxw

Do a general refresh of the main website to reflect persona work in these repos:
https://github.com/common-workflow-language/for_novices
https://github.com/common-workflow-language/for_novices

includes content, look, organization and navigation

This work can be funded by the EOSS CZI grant that Curii received.
I will work on this and then will work on a plan (early and often) of getting feedback :)

I will put links and ideas in conversation below.

https://search.google.com/search-console/mobile-usability/drilldown?resource_id=sc-domain%3Acommonwl.org&item_key=CAs&hl=en-DE&sharing_key=eB0gUJRGM5X49nZJtLxbig

Example: https://www.commonwl.org/v1.2/Workflow.html

@lunacodes can you open a PR to fix these soonish?
https://github.com/common-workflow-language/common-workflow-language.github.io/blob/21704381d24d5774a12deab9503fc4541c87ea66/linkchecker-report.txt

@tetron can you configure the website build to fail if there are broken links?

I noticed CWL-utils is in the utility section on the website, but it might be useful to also add it to the generators section as we generate pretty decent parsers + codegen.

Also, Python CWLGen has been deprecated (and archived), should we remove this from the list, or mark it deprecated in some way.

On the front page, using Firefox "view source" it is highlighting invalid HTML:

line 69: there is a dangling </nav> but there is no opening <nav>

the features grid has nested anchors (a <a> inside another <a>)
this seems to be due to using <h3> for the box titles, it is inserting <a href="#open-and-free" class="heading__anchor-symbol">§</a>
it probably shouldn't use <h3>, just a div with the appropriate styling.

/CWL-Logo-Header.png

…common-workflow-language/common-workflow-language.svg

…img/twitter.svg

https://web.dev/optimize-cls/#images-without-dimensions

Using https://github.com/common-workflow-language/logo/blob/master/cwl.mp4?raw=true

Wishlist:

• open source
• self-hosted
• mobile friendly
• subtitles
• minimal use of cookies, if at all

It would be nice if there is a link to Common Workflow Language Lab.
It is very helpful but currently I cannot find a link to CWL Lab from the official website.

Has black background on main page.

Missing elements in the gallery Page

@stain suggest using https://www.dropbox.com/s/1visx657xh1pmms/ELIXIR_logo_white_background.svg?dl=0

From the main page, the user should be able to easily find this github repo.

The spacing varies, based on whether a page has class: body-short or not.

Add Custom Video Player & Twitter Feed

Implement custom video player and Twitter feed, in order to avoid YouTube and Twitter's automatic tracking

• Replace embedded YouTube player with a custom video player
• Add subtitles and captions for video
• Create custom Twitter Feed

• Need to create a new section under https://www.commonwl.org/governance/ named "CWL Technical Team"
  The team is initially responsible for approving new versions of the CWL standards before that proposal goes to the CWL Leadership Team for the final vote.
• Collect ORCIDs as well

Confirmed members who have consented to being listed:

• Name: Iacopo Colonnelli
  Affiliation: University of Torino, Computer Science Dept.
  GitHub: https://github.com/glassofwhiskey
  Matrix: https://matrix.to/#/@glassofwhiskey:matrix.org
  ORCID: https://orcid.org/0000-0001-9290-2017
• Name: Michael R. Crusoe
  Affiliation: ELIXIR-NL
  GitHub: https://github.com/mr-c
  Matrix: https://matrix.to/#/@mr-c:matrix.org
  ORCID: https://orcid.org/0000-0002-2961-9670
• Name: Stian Soiland-Reyes
  Affilitaion: eScience Lab, The University of Manchester
  GitHub: https://github.com/stain
  Matrix: n/a
  ORCID: https://orcid.org/0000-0001-9842-9718
• Name: Fabrice Brito
  Affiliation: Terradue
  GitHub: https://github.com/fabricebrito
  Matrix: https://matrix.to/#/@fabrito:matrix.org
  ORCID: ???
• Name: Tomoya Tanjo
  Affiliation: Bioinformation and DDBJ Center, National Institute of Genetics
  GitHub: https://github.com/tom-tan
  Matrix: https://matrix.to/#/@tom-tan:matrix.org
  ORCID: https://orcid.org/0000-0002-4421-9659
• Name: Bogdan Gavrilović
  Affiliation: Seven Bridges
  GitHub: https://github.com/bogdang989
  Matrix: https://matrix.to/#/@bogdan_gavrilovic:matrix.org
  ORCID: https://orcid.org/0000-0003-1550-1716
• Name: Peter Amstutz
  Affiliation: Curii Corporation / Arvados
  GitHub: https://github.com/tetron
  Matrix: https://matrix.to/#/@tetron:matrix.org
  ORCID: https://orcid.org/0000-0003-3566-7705
• Name: Lon Blauvelt
  Affiliation: University of California Santa Cruz / Toil Project
  GitHub: https://github.com/DailyDreaming
  Matrix: https://matrix.to/#/@dailydreaming:matrix.org
  ORCID: https://orcid.org/0000-0001-8352-873X
• Name: Manabu Ishii
  Affiliation: Genome Analytics Japan Inc.
  GitHub: https://github.com/manabuishii
  Matrix: https://matrix.to/#/@manabuishii:matrix.org
  ORCID: https://orcid.org/0000-0002-5843-4712
• Name: Marius van den Beek
  Affiliation: Galaxy Project
  GitHub: https://github.com/mvdbeek
  Matrix: https://matrix.to/#/@mvdbeek:matrix.org
  ORCID: https://orcid.org/0000-0002-9676-7032

Yet to confirm: @johnbradley @michael-kotliar @pr80ik @audrium

GitHub Team: https://github.com/orgs/common-workflow-language/teams/tech_team
Matrix Room: https://matrix.to/#/#cwltool-dev:matrix.org

Convert commonwl.org to run off Jekyll, in order to facilitate a more straightforward future editing process. This will only affect the main site, and not the user documentation, at present.

• Rewrite site to utilize RWD (Responsive Web Design)
• Evaluate the site's WCAG Web Accesibility Guidelines compliance and implement any necessary fixes
• Evaluate site performance and implement any necessary improvements
• Incorporate new content
• Add Top Nav Menu and Site Footer
• Setup long-term staging/testing solution
• Incorporate custom Twitter feed
• Fill in SEO info in _config.yml

Where does the feedback go? Who can see it?

The meeting details on the new community page are not formatted by like the rest of the page.

• https://www.commonwl.org/community/

In general: Perhaps we don't need this on the community page but a link to a new page since it swallows up the rest of the resources of which the page was intended. We already have a mention of the weekly chat in the bullet points, so it is extra confusing. Perhaps that should link to a nicely formatted page about the meetings if people are interested.

To look like the rest of the page/general guidelines:
(1) Follow look and feel of rest of site

• Titles should be in all caps --> Agenda and Notes not Agenda and notes (and/if/but not caps)
• If you have a list of items --> Use the bullets
• We use numbers no where else on the site
• Periods only needed at end of sentences (https://w3id.org/cwl/meeting_minutes.)
• Hyperlinks should be given context (https://w3id.org/cwl/meeting_minutes.) and alt text instead of the direct link.
• Avoid long hyperlinks if possible: EMEA-Americas: weekly every Wednesday at 16:00 UTC from March-November and 17:00 UTC from November-March
• You should try to not have have section headers just start mid-page, for a good example to do this correctly see here: https://www.commonwl.org/features
• Balance new sections with existing format and content: Code of conduct already lives here: https://www.commonwl.org/code-of-conduct/ -- link to it perhaps in the list of bullet points above instead of having a new section for it.
• Consider making a new page when a topic seems to overwhelm the content of the page and/or is not of interest to all participants or very detailed on one topic
• Avoid hyperlinks when you can just put the detail easily on the page -- aka EMEA (Europe, the Middle East and Africa) is way more informative than linking to a wikipedia article. Same with APAC.

(2) Make things are new person/user friendly as possible: No explanation made about what the Weekly Meeting is, why one would attend or any context. Again, lots of work to make things as user-friendly in mind so we should keep doing this.

In general, we should have a review process since a bunch of work was made to make the website look good , organized, be approachable and consistent. Otherwise, I fear we will lose the headway we made quickly with the reformat.

11:22:55 AM: Downloading jekyll-4.1.1 revealed dependencies not in the API or the lockfile
11:22:55 AM: (kramdown (~> 2.1)).
11:22:55 AM: Either installing with --full-index or running bundle update jekyll should
11:22:55 AM: fix the problem.

Hi everyone. These are some things that I can't suggest directly as code changes.

• Should all links open in a new tab?
• On https://github.com/common-workflow-language/cwl-website/edit/new-site/content/_data/home.yml, the image in - icon: noun_ecosystem_cycle_3389565.png is going a bit over the word "reproducibility". That happened in Brave browser (Chromium-based) and Firefox on my Linux laptop.
• Should https://deploy-preview-75--cwl-website.netlify.app/assets/img/cwlportable.png say "FOSS" instead of "F/OSS"?
• Will https://deploy-preview-75--cwl-website.netlify.app/user_guide/ be a new page? It's linked in the Getting Started page but it still doesn't exist.
• Should the "Users Gallery" section be called "User Gallery" instead?

Also, some standards are needed:

• Decide whether to use the Oxford/Serial Comma or not
• What to do with the word "analys/ze"?
• In tables (ecosystem, projects) maybe always start paragraphs with a capital letter?

Please also see a compilation of my suggestions in this review: #75 (review)

EMEA-Americas: every Tuesday at 14:30 UTC

APAC: the second Tuesday of every month at 01:00 UTC

Link hrefs to anchors need to use _relative_url so they work properly, regardless of environment (staging, production, local, etc).

e.g.: [CWL leadership team]({{ site.url }}/#Leadership_Team) should be [CWL leadership team]({{ "#Leadership_Team" | relative_url }})

Here is the old text, that should replace (alphabetical) under https://www.commonwl.org/cwl-staging/#CWL_Leadership_Team

CWL is a member project of the Software Freedom Conservancy. In general, discussions about CWL should happen on open forums but you can also contact the CWL leadership team & Conservancy directly via [email protected]. This address should be CC'ed regarding all activities that involve activities of Common Workflow Language that related to things other than software development and documentation, and particularly any activities that expect to make use of Software Freedom Conservancy's non-profit status.

To contact just the CWL leadership team, please email [email protected].

The CWL leadership team consists of the following people, listed in alphabetical order by their last name:

User or Project name.
WorkflowHub

Section to list under
Cross-Domain

Link (URL) to website
https://www.workflowhub.eu

Description
WorkflowHub is a registry for describing, sharing and publishing scientific computational workflows.

The registry supports any workflow in its native repository.

WorkflowHub aims to facilitate discovery and re-use of workflows in an accessible and interoperable way. This is achieved through extensive use of open standards and tools, including Common Workflow Language (CWL), RO-Crate, BioSchemas and TRS, in accordance with the FAIR principles.

Logo or small graphic
https://workflowhub.eu/assets/logos/workflowhub-902d467e74d8797a4a2ac8313621208a1a2b215329e568e07b620baa03ed910b.svg

           <title>Matrix (protocol) logo</title>

This title shows up as a hover text for this icon on Firefox (non-mobile), but none of the other icons have a hover text.

If there is to be a hover text, I would prefer it said "CWL Matrix Space"

YouTube: "CWL YouTube Channel"
Twitter: "CWL Twitter Account"
GitHub: "CWL GitHub Organization"
Discourse: "CWL Discourse Forum"

Originally posted by @mr-c in #116 (comment)

We can make an issue template here. I think that would be the easiest way

Add a page to address how to use CWL with FAIR principals:

https://www.go-fair.org/fair-principles/

Some suggestion topics include:

• RO-Crate ( https://doi.org/10.5281/zenodo.4671709 )
• I believe @mr-c also has a document spelling this out from a more technical perspective he could link here

And how to edit the site