New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use HonoX #262
base: main
Are you sure you want to change the base?
feat: use HonoX #262
Conversation
@yusukebe, what do you think about this idea? |
1a9efd0
to
763473f
Compare
feat: add configuration file feat: add mock markdown chore: add command feat: add renderer & support mdx's title fix: add forgotten commands
763473f
to
5191c01
Compare
57085f2
to
844d120
Compare
Related to honojs/honox#86 |
e735407
to
1e9fe4b
Compare
Hi @goisaki This is an awesome challenge! I respect you for trying to do this! Personally, I would prefer to continue using VitePress to lower maintenance costs, but I am eager to support this challenge. Actually, VitePress very well and quickly transitions pages using the SPA approach. However, even serving HTML is fast enough if distributed from the edge, so this should not be a problem. We want others' opinions, ideas, and help! |
2cc1f59
to
29ae982
Compare
@yusukebe |
fix: add missed imports fix: fix broken syntax highlighting in vscode feat: add auto-generated title to front matter feat: rename `.md` to `.mdx` fix: fix routes
3632391
to
4a5951d
Compare
@yusukebe |
The reason why it is hard-coded is to prevent extensions other than the expected ones. But, allowing |
Hmmm, I've tried locally, but I can't seem to find a simple, minimalist way to do it.
Also, the addition of the sample project, which is the original purpose, has fortunately already been done in So I am beginning to think this PR is unnecessary. |
No problem!! You are challenge is awesome.
SPA may be difficult, but I feel it can be done for other things. Also, we can improve HonoX to do that. You may leave this PR if you like. Anyway, what you have done is not a waste. Thank you so much! |
Everyone wants Hono documents to be by Hono.
According to file-based routing by HonoX, it is possible.
It will be interesting to see if this can be an example of a project by HonoX & Hono.
(It should be noted that HonoX is not yet stable.)