Customizing the location of page chunks #567
-
|
Hello! I'm just getting started with Vuepress and am evaluating if this is going to be a good fit for my use case. The initial impressions are promising, but I've a concern. I am trying to work on a protected and private documentation website. The contents of it should not be available without authentication. I am going to gate access with Netlify's Role Based Access Control. I've set up the roles and redirects for server-side auth. That's working fine. To prevent client-side routing, I'm using NavigationGuards along with a Vuex store (it simply stores if the user is authenticated). However, there remains a last part of the problem. The chunks exported by Webpack have the content of the Markdown files pretty easily visible. For example, I got this as the export:
This is one of the files in So, if the above is not possible, what do all the fellow developers recommend when trying to setup a sensitive documentation? Looking forward to some great advice. P.S.: Please ignore |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Sorry for the late reply, but if you want acess controll, you should never consider "A static site generator", you probably need to choose those with backend. Those tool may give you opportunity to dynamicly render markdown content, and they are surely more secure than tools like vitepress or vuepress. Also people may only concern which folder does all the static files been generated (to avoid conflict), instead of their structure and file names, so your request is probably more like an edge case, and may out of our consideration. |
Beta Was this translation helpful? Give feedback.
Sorry for the late reply, but if you want acess controll, you should never consider "A static site generator", you probably need to choose those with backend. Those tool may give you opportunity to dynamicly render markdown content, and they are surely more secure than tools like vitepress or vuepress.
Also people may only concern which folder does all the static files been generated (to avoid conflict), instead of their structure and file names, so your request is probably more like an edge case, and may out of our consideration.