-
Notifications
You must be signed in to change notification settings - Fork 1
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
Site design currently broken #4
Comments
I am very much leaning towards the view that we simply don't need |
Yeah. Only issue (at least in my case) is that my project has multiple docs, due to it being split into modules, so instead of just having like But I mentioned this on the Discord that I'm currently leaning towards turning my mess of a code into a single-module project to get rid of a lot of limitations, issues and similar, so that issue above can imo be safely ignored. |
I'm imagining that those can stay under |
Yeah, that would be fine by me. |
Question now: Would we just like archive this repo once it's no longer needed, or would it be removed? I personally don't see any real value in having this repo staying here... |
The repo needs to stay so that the |
Due to the changes made to the main BotBlock Website is the
docs.botblock.org
website completely broken in its design.We should find a way to repair it and make it the same look as the BotBlock website itself.
The question now is, how can we do this the best way?
One way could perhaps be to make it like the Best Practices by having a
.vue
file for it in static-site and pull from theindex.md
here to generate the page.Downside could be, that we no longer have the page under the
docs
subdomain, unless we use that instead or implement redirects for it.Also, this would open the question if it is even worth keeping the separate docs branch, as the only other page existing would be the one for JavaBotBlockAPI which itself only uses it for hosting the Java code documentation (Javadocs), which I think could be supported in the same way as the Best Practices page?
Either way would it be good to find a solution here to get this resolved in some reasonable way.
The text was updated successfully, but these errors were encountered: