@@ -0,0 +1,36 @@
|
||||
---
|
||||
# https://vitepress.dev/reference/default-theme-home-page
|
||||
layout: home
|
||||
|
||||
hero:
|
||||
name: "XO Stack"
|
||||
text: "XO Stack"
|
||||
tagline: My great project tagline
|
||||
actions:
|
||||
- theme: brand
|
||||
text: Quick Start
|
||||
link: /markdown-examples
|
||||
- theme: alt
|
||||
text: APIs
|
||||
link: /api
|
||||
|
||||
features:
|
||||
- title: Feature A
|
||||
details: Lorem ipsum dolor sit amet, consectetur adipiscing elit
|
||||
- title: Feature B
|
||||
details: Lorem ipsum dolor sit amet, consectetur adipiscing elit
|
||||
- title: Feature C
|
||||
details: Lorem ipsum dolor sit amet, consectetur adipiscing elit
|
||||
---
|
||||
|
||||
I haven't played with custom theming much yet and have been working with more the configuration side of things for Docs.
|
||||
|
||||
However, it does seem like there's quite a lot of flexibility with VitePress.
|
||||
|
||||
We probably won't want to create an entirely custom theme, but extend the default instead:
|
||||
|
||||
https://vitepress.dev/guide/extending-default-theme
|
||||
|
||||
Also, don't take what's in these docs here literally. I'm still toying around with things.
|
||||
|
||||
But having the API docs generate is probably quite useful in even the early-dev/experimental phase: It allows us to get a feel for the API.
|
||||
Reference in New Issue
Block a user