Skip to content

Future plans regarding V4 #149

@Funasitien

Description

@Funasitien

Hi ! I wanted to clean a bit the documentation to preapare it for the latest releases of CloudNet, but I would have some questions first, related to the global structure & markdown compiler.

First, do you still want to have both complete versioning and languages support? I do fear that such a structure start to look messy, as you have languages×versions markdow pages, which is a lot. This is a discussion, I do not have the perfect solution, but maybe the aproach of tailwindcss and daisyui, where only the latest major versions are suported, would be a bit eaysier to handle. Also, if you only provide support to the latest release, it's more logic to do so.

Then, the markdown compiler. Do you want to stick on docusaurus or maybe switch to a more modern alternative? Here, Astro could be a interesting idea as you use a lot of custom pages, but others such as vitepress could also be considered

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions