Dynamic info in progress

hcourdent · hcourdent · commit 4c46aa8ed57c · 2023-12-07T15:11:52.000+01:00
diff --git a/blog/2023-06-05-discord-bot/index.mdx b/blog/2023-06-05-discord-bot/index.mdx
@@ -121,7 +121,16 @@ We need to ingest a data source, here the [Windmill documentation](/docs/intro).
 
 :::info Workflows
 
-A [workflow](/docs/flows/flow_editor) is a series of connected tasks, events, or processes that occur automatically to achieve a specific goal. These tasks are organized as a sequence of actions or steps: [scripts](/docs/getting_started/scripts_quickstart) in the case of Windmill.
+[Workflows](/docs/flows/flow_editor) are graphs ([DAG](https://en.wikipedia.org/wiki/Directed_acyclic_graph)) that represent the dependencies between steps.
+
+<br/>
+
+The goal of an orchestrator or workflow engine is to execute the steps on different workers that respect that graph's dependencies, and pass the required data defined in the steps' inputs while applying parallelism when possible.
+
+<br/>
+
+In Windmill, each step is [code](/docs/getting_started/scripts_quickstart) with a main function in TypeScript, Python, Go, Bash or raw queries to databases.
+
 :::
 
 ![Flow](./flow.png.webp 'Create a scheduled flow that scrapes the Windmill documentation')
diff --git a/blog/2023-11-20-ai-flow-builder/index.mdx b/blog/2023-11-20-ai-flow-builder/index.mdx
@@ -85,9 +85,9 @@ We are using [GPT-4-turbo (1106-preview version)](https://platform.openai.com/do
  
 ## What are Windmill Flows?
 
-Workflows are graphs ([DAG](https://en.wikipedia.org/wiki/Directed_acyclic_graph)) that represents the dependencies between steps.
-The goal of an orchestrator or workflow engine is to execute the steps on different workers that respect that graph dependencies, and pass the required data defined in the steps' inputs while applying parallelism when possible.
-In Windmill, each step is code with a main function in typescript, python, go, bash or raw queries to databases.
+Workflows are graphs ([DAG](https://en.wikipedia.org/wiki/Directed_acyclic_graph)) that represent the dependencies between steps.
+The goal of an orchestrator or workflow engine is to execute the steps on different workers that respect that graph's dependencies, and pass the required data defined in the steps' inputs while applying parallelism when possible.
+In Windmill, each step is code with a main function in TypeScript, Python, Go, Bash or raw queries to databases.
 
 The primitives supported by Windmill workflows are:
 
diff --git a/docs/core_concepts/10_error_handling/index.mdx b/docs/core_concepts/10_error_handling/index.mdx
@@ -84,7 +84,7 @@ You can pick the Slack pre-set schedule error handler or define your own.
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
-		title="Scheduling"
+		title="Schedules"
 		description="Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies."
 		href="/docs/core_concepts/scheduling"
 	/>
diff --git a/docs/core_concepts/1_scheduling/index.md b/docs/core_concepts/1_scheduling/index.md
@@ -1,4 +1,4 @@
-# Scheduling
+# Schedules
 
 Windmill provides the same set of features as CRON, but with a user interface and control panels. It allows you to define Schedules for Scripts and Flows. Once a schedule is defined, the script will automatically run at the set frequency. Think of it as an easy-to-use scheduler similar to CRON that you can share with other users.
 
diff --git a/docs/core_concepts/4_webhooks/index.mdx b/docs/core_concepts/4_webhooks/index.mdx
@@ -15,7 +15,7 @@ Some use cases include triggering scripts and flows from [Slack](/blog/handler-s
 
 :::
 
-Each Script and Flow created in the app gets autogenerated webhooks. The webhooks depend on how they are triggered, and what their return values are.
+Each Script and Flow created in Windmill gets autogenerated webhooks. The webhooks depend on how they are triggered, and what their return values are.
 
 ## Addresses
 
diff --git a/docs/core_concepts/index.mdx b/docs/core_concepts/index.mdx
@@ -58,7 +58,7 @@ On top of its editors to build endpoints, flows and apps, Windmill comes with a
     	href="/docs/core_concepts/collaboration"
     />
     <DocCard
-    	title="Scheduling"
+    	title="Schedules"
     	description="Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies."
     	href="/docs/core_concepts/scheduling"
     />
diff --git a/docs/flows/1_flow_editor.mdx b/docs/flows/1_flow_editor.mdx
@@ -5,10 +5,12 @@ import { Timer, TerminalSquare } from 'lucide-react';
 
 Windmill's Flow Editor allows you to build flows with a low-code builder.
 
-:::info Workflows
+Workflows are graphs ([DAG](https://en.wikipedia.org/wiki/Directed_acyclic_graph)) that represent the dependencies between steps.
+
+The goal of an orchestrator or workflow engine is to execute the steps on different workers that respect that graph's dependencies, and pass the required data defined in the steps' inputs while applying parallelism when possible.
+
+In Windmill, each step is code with a main function in TypeScript, Python, Go, Bash or raw queries to databases.
 
-A workflow is a series of connected tasks, events, or processes that occur automatically to achieve a specific goal. These tasks are organized as a sequence of actions or steps: [scripts](../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx) in the case of Windmill.
-:::
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
diff --git a/docs/flows/3_editor_components.mdx b/docs/flows/3_editor_components.mdx
@@ -93,7 +93,7 @@ Have more details on all the ways to trigger flows [here](../getting_started/9_t
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
 		color="teal"
-		title="Scheduling"
+		title="Schedules"
 		description="Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies."
 		href="/docs/core_concepts/scheduling"
 	/>
diff --git a/docs/getting_started/6_flows_quickstart/index.mdx b/docs/getting_started/6_flows_quickstart/index.mdx
@@ -53,7 +53,7 @@ On another tab, you can configure a [Schedule](../../core_concepts/1_scheduling/
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
 		color="teal"
-		title="Scheduling"
+		title="Schedules"
 		description="Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies."
 		href="/docs/core_concepts/scheduling"
 	/>
diff --git a/docs/getting_started/8_trigger_scripts/index.mdx b/docs/getting_started/8_trigger_scripts/index.mdx
@@ -122,7 +122,7 @@ You can create schedules by specifying a script or flow, its arguments, and a CR
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
-    	title="Scheduling"
+    	title="Schedules"
     	description="Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies."
     	href="/docs/core_concepts/scheduling"
     />
diff --git a/docs/getting_started/9_trigger_flows/index.mdx b/docs/getting_started/9_trigger_flows/index.mdx
@@ -96,7 +96,7 @@ You can create schedules by specifying a script or flow, its arguments, and a CR
 
 <div class="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
-		title="Scheduling"
+		title="Schedules"
 		description="Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies."
 		href="/docs/core_concepts/scheduling"
 	/>
diff --git a/docs/script_editor/index.mdx b/docs/script_editor/index.mdx
@@ -7,7 +7,7 @@ import TabItem from '@theme/TabItem';
 In Windmill, Scripts are the basis of all major features (they are the steps of [flows](../getting_started/6_flows_quickstart/index.mdx), [linked to apps components](../apps/3_app-runnable-panel.mdx), or can be [run as standalone](../getting_started/8_trigger_scripts/index.mdx)).
 
 A Script can be written in:
-[TypeScript (Deno)](../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx),
+[TypeScript (Deno & Bun)](../getting_started/0_scripts_quickstart/1_typescript_quickstart/index.mdx),
 [Python](../getting_started/0_scripts_quickstart/2_python_quickstart/index.mdx),
 [Go](../getting_started/0_scripts_quickstart/3_go_quickstart/index.mdx),
 [Bash](../getting_started/0_scripts_quickstart/4_bash_quickstart/index.mdx) or
diff --git a/docs/script_editor/script_kinds.mdx b/docs/script_editor/script_kinds.mdx
@@ -38,7 +38,7 @@ changes,it _triggers_ the rest of the flow, i.e. subsequent Scripts.
 		href="/docs/flows/flow_trigger"
 	/>
 	<DocCard
-		title="Scheduling"
+		title="Schedules"
 		description="Windmill provides the same set of features as CRON, but with a user interface and control panels."
 		href="/docs/core_concepts/scheduling"
 	/>
diff --git a/src/components/Solutions.tsx b/src/components/Solutions.tsx
@@ -8,6 +8,7 @@ import { Helmet } from 'react-helmet-async';
 import { useColorMode } from '@docusaurus/theme-common';
 import SolutionSVG from './SolutionSVG.svg';
 
+
 function Screenshot({ darkScreenshot, lightScreenshot }) {
 	const { colorMode } = useColorMode();
 	const screenshot = colorMode === 'dark' ? darkScreenshot : lightScreenshot;
diff --git a/src/css/custom.css b/src/css/custom.css
@@ -410,3 +410,14 @@ div.testimonials a:hover .wm-name {
 .hover-change-color:hover {
     fill: #F0F0F0
 }
+
+.hover-darker-color:hover {
+    filter: brightness(80%);
+}
+.group-darker-change-color:hover {
+    filter: brightness(80%);
+}
+
+.image-hover-change-color:hover {
+    filter: brightness(80%);
+}
diff --git a/src/landing/Hero.jsx b/src/landing/Hero.jsx
@@ -2,6 +2,7 @@ import React from 'react';
 import GithubStarCount from './GithubStarCount';
 import RadialBlur from './RadialBlur';
 import { useColorMode } from '@docusaurus/theme-common';
+import HomescreenSvg from '../../static/homescreen.svg';
 
 export default function Hero() {
 	const { colorMode } = useColorMode();
@@ -65,14 +66,9 @@ export default function Hero() {
 				</div>
 				<div className="mx-auto mt-16 sm:mt-8">
 					<div className="flex-none !rounded-2xl overflow-hidden dark:bg-[#2e344033]">
-						<img
-							src={colorMode === 'dark' ? '/homescreen-dark.svg' : '/homescreen.svg'}
-							alt="Windmill infrastructure"
-							className="w-full"
-							width="1825"
-							height="1920"
-							loading="lazy"
-						/>
+					<div className="svg-container">
+						<HomescreenSvg className="scaled-svg" style={{ width: '90%', height: '90%' }} />
+					</div>
 					</div>
 				</div>
 			</div>
diff --git a/static/homescreen.svg b/static/homescreen.svg

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# Scheduling`
	`1`	`+# Schedules`
`2`	`2`
`3`	`3`	`Windmill provides the same set of features as CRON, but with a user interface and control panels. It allows you to define Schedules for Scripts and Flows. Once a schedule is defined, the script will automatically run at the set frequency. Think of it as an easy-to-use scheduler similar to CRON that you can share with other users.`
`4`	`4`