Refactor website to use Hugo and Docsy; Add a blog

[ricardozanini]

Many thanks for submitting your Pull Request ❤️!

What this PR does / why we need it:

• Fix Create Blog #199
• Fix Refactor Website #198
• Fix Website does not have the correct trademark disclaimer #196

Special notes for reviewers:
Still, work todo:

• Add CI to preview the changes on Netlify (depends on https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-2321)
• Add schemas from previous version and 1.0.0-*
• Fix favicons
• Fix link cards preview

Additional information (if needed):

[cdavernas]

LGTM! Many thanks man ❤️

[cdavernas]

Aside from the ordering comment, I think we should re-add the sponsors section, both in the website and the spec.

Even though Neuroglia is for now the only sponsor of the project (and as part of the latter I'm therefore biased), it did sponsor the project, and should therefore clearly appear as such, which also might incentivise others to move in.

We should also add a "buy us a coffe" kind of button, on both website and spec. Donators should also be visibly and explicitly thanked for their donations, and be tracked somewhere in the repo. The money we obtain should be invested for marketing and communication purpose, in other to grow our user base and widen adoption for the further stage of SW in the CNCF.

[ricardozanini]

@cdavernas can you take another review?

[cdavernas]

Looks great to me, many thanks!
Do you think you could display the other key features on the index, and provide small code snippets, like now?

[ricardozanini]

Looks great to me, many thanks! Do you think you could display the other key features on the index, and provide small code snippets, like now?

I would need help with HTML + js to be able to use this: https://www.docsy.dev/docs/adding-content/shortcodes/#tabbed-panes

It appears, but breaks the page. I think it's not meant to be used on the landing page. So maybe @JBBianchi could help in a future PR? I will take a lot of time to do it, which I don't have atm.

What other key features you mean?

[JBBianchi]

Looks great to me, many thanks! Do you think you could display the other key features on the index, and provide small code snippets, like now?

I would need help with HTML + js to be able to use this: https://www.docsy.dev/docs/adding-content/shortcodes/#tabbed-panes

It appears, but breaks the page. I think it's not meant to be used on the landing page. So maybe @JBBianchi could help in a future PR? I will take a lot of time to do it, which I don't have atm.

What other key features you mean?

Sure, we can have a look together.

[cdavernas]

What other key features you mean?

We have a lot more of those in the Readme:

• Easy to Use: Designed for universal understanding, Serverless Workflow DSL enables users to quickly grasp workflow concepts and create complex workflows effortlessly.
• Event Driven: Seamlessly integrate events into workflows with support for various formats, including CloudEvents, allowing for event-driven workflow architectures.
• Service Oriented: The Serverless Workflow DSL empowers developers to seamlessly integrate with service-oriented architectures, allowing them to define workflows that interact with various services over standard application protocols like HTTP, GRPC, OpenAPI, AxsyncAPI, and more.
• FaaS Centric: Seamlessly invoke functions hosted on various platforms within workflows, promoting a function-as-a-service (FaaS) paradigm and enabling microservices architectures.
• Timely: Define timeouts for workflows and tasks to manage execution duration effectively.
• Fault Tolerant: Easily define error handling strategies to manage and recover from errors that may occur during workflow execution, ensuring robustness and reliability.
• Schedulable: Schedule workflows using CRON expressions or trigger them based on events, providing control over workflow execution timing.
• Interoperable: Integrates seamlessly with different services and resources.
• Robust: Offers features such as conditional branching, event handling, and looping constructs.
• Scalable: Promotes code reusability, maintainability, and scalability across different environments.

And possibly even others worth mentioning...

[ricardozanini]

@cdavernas sure we can add them all, but don't you think it will get cluttered? Maybe 3 more to have an additional line?

[cdavernas]

@ricardozanini Yeah, you are right. Maybe 3 more indeed

[ricardozanini]

@cdavernas I'll let you pick the other 3. 😛

[cdavernas]

Let's pick the 6 first, no? They feel like the most compelling to me.

[ricardozanini]

@cdavernas if you're happy with the content now, feel free to merge :)

[ricardozanini]

@JBBianchi @cdavernas btw I created an issue to track the code section: #203

[ricardozanini]

@cdavernas one last thing: I've added the schema to the schemas section with both YAML and JSON versions. 👍