-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: toggle hardcoded schema versions (#5)
- Loading branch information
Showing
5 changed files
with
180 additions
and
49 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
import Box from "@mui/material/Box"; | ||
import Typography from "@mui/material/Typography"; | ||
|
||
import { Provider as MosaicProvider, injectStyles } from "@stoplight/mosaic"; | ||
|
||
import { ComponentProps } from "react"; | ||
|
||
const Header = ({ children }: ComponentProps<"header">) => { | ||
injectStyles(); | ||
|
||
return ( | ||
<Box p={2} style={{ maxWidth: 1000 }} mx="auto"> | ||
<Typography textAlign="center" variant="h2"> | ||
Digital planning data schemas | ||
</Typography> | ||
<Typography pt={4} maxWidth={800} mx="auto"> | ||
Digital Planning Data schemas aim to encourage more interoperability and | ||
consistency between systems by offering a central, version controlled | ||
specification for documenting and validating planning data. | ||
</Typography> | ||
<MosaicProvider> | ||
<Box | ||
p={6} | ||
my={4} | ||
maxWidth={800} | ||
style={{ | ||
borderRadius: 2, | ||
backgroundColor: "#fff5ef", | ||
}} | ||
mx="auto" | ||
> | ||
{children} | ||
</Box> | ||
</MosaicProvider> | ||
</Box> | ||
); | ||
}; | ||
|
||
export default Header; |