serverlessworkflow / serverlessworkflow.github.io Goto Github PK

On the subpage "Execute your production workflows" of the index page "https://serverlessworkflow.io/"，The link of "EventMesh workflow" is expired.The git repo has been moved to https://github.com/apache/incubator-eventmesh along side Apache EventMesh already has its own official website on https://eventmesh.apache.org/

Site still points to schema hosted in github

Why is this needed:

https://serverlessworkflow.io in the README.md redirects to https://cncf.github.io/wg-serverless-workflow/, which is not existing anymore.

It should be https://serverlessworkflow.github.io/.

What would you like to be added:
Consider reducing length of 'accessibility paragraph' on cloudevents.io. 1-paragraph is longer than the other two. 2-the second sentence could be added somewhere else. 3- first sentence could be improved (No common event format means there are no common libraries, tooling, and infrastructure for delivering event data across cloud environments.)
Why is this needed:
See above. On desktop then 'accessibility' is out of balance with the two other sections.
Accessibility

No common event format means no common libraries, tooling, and infrastructure for delivering event data across environments. CloudEvents provides SDKs for Go, JavaScript, Java, C#, Ruby, and Python that can be used to build event routers, tracing systems, and other tools.

What would you like to be added:

Refactor the website, as suggested by @ricardozanini.

Why is this needed:

Adapt to current design goals.
Modernize the UI.

What would you like to be added:

Cretae a blog dedicated to Serverless Workflow, as suggested by @ricardozanini.

Why is this needed:

• Publish important information, such as releases.
• Publish tutorials
• Publish articles
• ...

What would you like to be added:
Request to add the Workflow Runtime implementation: serverlessworkflow-go.

Project materials:
Project logo: https://sw-1251681900.cos.ap-singapore.myqcloud.com/em.png
Project name: EventMesh Workflow
Project Description: EventMesh Workflow is a cloud vendor-independent, cloud-native-oriented Serverless Workflow Runtime based on Serverless Workflow specification, and provides durability, reliability, scalability, and observability capabilities.

What would you like to be added:
It seems the link to the specification's schemas don't exist anymore, it would be nice to have them.

Why is this needed:

1. They exist/are hosted on the website
2. It's the id used in the schemas
3. It would prevent the user from having to find them on GitHub.

What would you like to be added:
I would like to be o load the schemas form the website but CORS policies prevent me to do so. It would be nice to disable them.

Why is this needed:
For foreign sites to load the resources.

Currently, the website's editor utilizes a serverless workflows specification DSL to generate flowchart diagrams. However, the code in the GitHub repository for the editor is only available in minified form. This makes it incredibly challenging for contributors to understand, read, or contribute effectively to the project.

What would you like to be added:
Provide a clear link from from cloudevents.io to https://serverlessworkflow.io/
Why is this needed:
I could not see an obvious link. Also serverlessworkflow.io has more dynamic/updated content, cloudevents.io lacks recent progress updates (Twitter and GitHub not that active).

As part of our ongoing effort to cncf/techdocs#198, we noticed that the website does not pass the trademark criteria on CLOMonitor.

To fix this:
Head to the source code of the website. In the <footer> section, add a disclaimer or link to the Linux foundation trademark disclaimer page:

Disclaimer

<footer>
   <p>The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, 
         please see our <a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademark Usage page</a>.
   </p>
</footer>

Link

 <footer>
      <ul>
          <li><a href="https://www.linuxfoundation.org/legal/trademark-usage">Trademarks</a></li>
      </ul>
 </footer>

What would you like to be added:
Links to lower sections from top nav e.g. 'what...' and 'contribute...'
Why is this needed:
A great design, key content could be easier to find.

1. move the site to Netlify so you can get PR previews

2. also take advantage of Netlify DNS

What would you like to be added:
We have errors namespaced by our domain in the new DSL: https://github.com/serverlessworkflow/specification/blob/main/dsl-reference.md#standard-error-types

It would be nice to have them documented (dynamically, by using CI) on the website as well.

Why is this needed:
Users can fetch the error-rich description by accessing the URL when seeing the log in a runtime implementation

What would you like to be added: Updated information about Red Hat

What would you like to be added:
Consider reducing hero-body vertical padding (on desktop and mobile)
Why is this needed:
A great design but it is not obvious there is important content out of sight. See related issue.

Notice from Netlify

After November 15, 2022, builds for this site will fail unless you update the build image.

As reported via deploy logs:

DEPRECATION NOTICE: Builds using the Xenial build image will fail after November 15th, 2022.

The build image for this site uses Ubuntu 16.04 Xenial Xerus, which is no longer supported.
All Netlify builds using the Xenial build image will begin failing in the week of November 15th, 2022.

To avoid service disruption, please select a newer build image at the following link:
https://app.netlify.com/sites/etcd/settings/deploys#build-image-selection

For more details, visit the build image migration guide:
https://answers.netlify.com/t/please-read-end-of-support-for-xenial-build-image-everything-you-need-to-know/68239