earthquake.usgs.gov

A tsunami is a series of ocean waves caused by a large disturbance of the sea floor or the water above it — most often an undersea earthquake, but also undersea volcanic eruptions, landslides, or meteorite impacts. In Victoria, tsunami is one of the emergencies VICSES (Victoria State Emergency Service) plans and responds for, alongside flood, storm, earthquake and landslide. If you are in Victoria and a tsunami warning is issued, your priority is to move away from the coast and low-lying areas, follow official warnings from VicEmergency and the Bureau of Meteorology (BOM), and only call 132 500 for VICSES assistance — not for life-threatening emergencies, which go to Triple Zero (000).

How a tsunami forms and how it behaves

A tsunami is not a single wave. It arrives as a series of waves, and the first one is often not the largest. Key characteristics:

• Trigger: Usually a shallow, large undersea earthquake that displaces a column of water. Landslides and volcanic activity can also generate tsunamis.
• Speed and height: In deep ocean, tsunami waves can travel at jet-aircraft speed but with small height. As they reach shallower coastal water, they slow and grow.
• Timing between waves: Waves can arrive minutes to hours apart, so the danger can persist long after the first impact.
• Local vs. distant source: A tsunami generated close to shore may arrive within minutes, leaving little time for official warnings. A distant-source tsunami gives more warning time.

Is tsunami a real risk in Victoria?

VICSES treats tsunami as one of the emergencies it plans for across Victoria, and the agency publishes tsunami guidance under its "Plan and stay safe" section. Victoria's exposure is mainly through its coastline and low-lying coastal areas, and the risk can come from either distant or nearby undersea events. Because tsunami is listed alongside flood, storm, earthquake and landslide as a VICSES responsibility, the practical takeaway is that coastal communities should include tsunami in their emergency planning rather than assume it cannot happen.

For local risk detail, VICSES directs people to its Local Flood Guides for understanding local flood risk, and its broader emergency pages for tsunami. Use the tsunami page on the VICSES site as your starting point for official Victorian guidance.

Warning signs you should act on

You may have little or no official warning, especially for a local-source tsunami. Treat any of these as a cue to move inland and to higher ground:

• Strong or prolonged shaking from an earthquake near the coast.
• A sudden rise or fall in sea level, or the sea receding unusually far and exposing the sea floor.
• A loud roar from the ocean, like a train or aircraft.
• An official tsunami warning from VicEmergency or BOM.

Do not go to the beach to watch. Tsunami waves and strong currents are dangerous, and the first wave may not be the biggest.

What to do before, during and after

Before

• Know your route: Identify how you would get inland and to higher ground from where you live, work or holiday. VICSES stresses planning for emergencies at home, at work, at school and on holidays.
• Create an emergency plan: VICSES provides a "Create an emergency plan" resource so households and workplaces can decide in advance what they will do.
• Understand warnings: Learn how VicEmergency and BOM warnings are issued and what they mean, so you can act quickly.
• Check local guides: Review the Local Flood Guides and VICSES tsunami information for your area's specific risk.

During

• Move away from the coast and low-lying areas immediately — go inland and to higher ground.
• Follow official instructions from VicEmergency and BOM. If told to evacuate, do so.
• Stay out of the water and off beaches, and keep away from harbours, rivers and estuaries, where tsunami currents can be strong.
• Do not return until authorities say it is safe; multiple waves can arrive over an extended period.

After

• Wait for the all-clear from official sources before returning to coastal areas.
• Avoid damaged areas and debris, and stay clear of floodwater and contaminated water.
• Check on others if it is safe to do so, and follow VICSES recovery guidance after an emergency.
• Report damage or request assistance through the correct channels (see below).

Who to call and where to get warnings

VICSES lists these contact points together: VicEmergency warnings, BOM weather and warnings, flood and storm emergencies on 132 500, and life-threatening emergencies on Triple Zero (000). Note that 132 500 is for VICSES assistance — it is not the number for a life-threatening emergency.

Practical checklist for coastal Victorians

• [ ] Confirm whether you live, work or holiday in a tsunami-risk coastal or low-lying area.
• [ ] Read the VICSES tsunami page and your Local Flood Guide.
• [ ] Write an emergency plan using the VICSES "Create an emergency plan" resource.
• [ ] Identify your inland/higher-ground route and a meeting point.
• [ ] Set up VicEmergency and BOM as your warning sources.
• [ ] Know the difference: 132 500 for VICSES help, 000 for life-threatening emergencies.

The core message is simple: tsunami is a recognised emergency in Victoria, warnings may be short, and the safe response is to move inland and to higher ground while following official VicEmergency and BOM advice.

Plate is an open-source React framework for building rich-text editors, built on top of Slate. It gives you a set of customizable plugins and components rather than a finished WYSIWYG widget, so it fits projects where you need control over behavior and design. If you want a drop-in editor with no assembly required, Plate is probably more framework than you need; if you want to compose an editor from parts, it is a reasonable starting point.

What Plate actually provides

Plate sits between Slate (the underlying editor engine) and your application. Slate handles the document model and editing primitives; Plate adds the structure that makes those primitives practical to assemble:

• Plugins — discrete pieces of editor behavior you opt into, rather than a monolithic feature set.
• Components — prebuilt UI pieces for the editor surface, designed to be restyled.
• Framework integration — it targets React, and the site lists Next.js among its keywords, so it fits standard React app structures.
• Design-system alignment — the components are described as beautifully designed and customizable, with integrations named for Tailwind CSS, Radix UI, and shadcn/ui.

The practical consequence: you are not choosing between "has bold" and "doesn't have bold." You are choosing which plugins to register and how to render them.

How to start

The site's own preview shows a single-command path for a ready-made editor:

npx shadcn@latest add @plate/editor-ai

That command pulls in a Plate editor setup through the shadcn CLI. The result is a working editor you can then modify — the site presents it alongside a live preview and a code view, with an "Open in New Tab" and "Refresh Preview" option for inspecting the running result.

What to expect at each stage:

1. Run the command in your project. It adds the editor files through the shadcn mechanism, so your project should already be set up for that workflow.
2. Open the generated editor component. You get a composed editor rather than an empty shell — the example is an AI editor, so it includes AI-related wiring.
3. Render it in your app and confirm it mounts. The preview on the site is the reference for what a working instance looks like.
4. Adjust plugins and components to match your requirements. This is the step where Plate differs from a widget: the feature set is something you edit, not something you configure through a settings object.

Where Plate fits and where it doesn't

The deciding question is whether editor behavior is part of your product's value. If it is, the plugin-and-component model pays off. If the editor is incidental, the assembly cost is hard to justify.

Key mechanics worth understanding

Plugin input rules. The site lists "Plugin Input Rules" as a concept. These are the rules that turn typed patterns into structured content — the mechanism behind behaviors like typing a marker and getting a formatted block. Because they are plugin-scoped, you control which input transformations exist in your editor.

Composition over configuration. Plate's model is that an editor is the sum of its plugins and components. Adding a capability means adding a plugin; changing appearance means changing components. This is why the framework suits teams with opinions about their editor and frustrates teams without them.

Slate underneath. Because Plate builds on Slate, the document model and low-level editing behavior come from Slate. If you already know Slate, Plate's abstractions will read as a layer on familiar ground.

A concrete scenario

Suppose you are building a Next.js app where users write structured notes, and you want the editor to match your existing shadcn/ui components exactly. With Plate you would add the editor via the shadcn CLI, then replace or restyle the provided components so they use your design tokens, and register only the plugins your note format needs. The output is an editor that looks like the rest of your app and supports exactly your content types — which is the outcome Plate is designed to produce.

If instead you needed a comment box with basic formatting and no design constraints, the same setup work would be overhead.

What to check before committing

• Confirm your project is React-based and compatible with the shadcn CLI workflow, since that is the documented starting path.
• Review the plugin list against the features you actually need, and note which ones you would have to write yourself.
• Check the component layer against your design system — the named integrations (Tailwind CSS, Radix UI, shadcn/ui) suggest the intended pairing.
• The site presents itself as open source; verify current licensing and maintenance activity in the repository before depending on it long-term.