If you rename index.md to _index.md, all files in the directory are rendered upon build. └── _index.md -> This makes it a branch bundle This is a branch bundle: src/docu/components/accordion/
![html iframe source code not accessible html iframe source code not accessible](https://i.ytimg.com/vi/MhODHoaats0/maxresdefault.jpg)
Make the same change to the other shortcode calls on this page. In src/docu/components/accordion/index.md you have: That’s better, but you’ve got another problem. Now remove the front matter from each of the files, and run the command again. You can see that the accordion*.html files are missing from the directory. So those files are rendered as content and then discarded because, in a leaf bundle, there can only be one content page (source is index.md).Ĭommand rm -rf dist & npm run docu:build & tree dist/docu/components/accordion Looking at this structure, it would seem that the HTML files are page resources, and if properly linked, everything would work as desired.īut instead of being just dumb chunks of HTML, you have added front matter to each of the HTML files. └── index.md -> This makes it a leaf bundle Your content is a currently a leaf bundle: src/docu/components/accordion/ Step 1: Setting up the servers for our demo application Applying the sandbox attribute to the iframe and exploring the various options for the sandbox.Embedding the content of our client page in an iframe on the host page and investigating what the client iframe is and is not allowed to do.Setting up two node servers to simulate two different. Read this entire post before making any changes. It’s much easier to see what’s happening when looking at the repository: Hugo simply does not recognize the files accordion-basic.html, etc., regardless of whether I make *.md files out of them, add them to the menu ( src/assets/hugo/config/_default/menus.toml ) or add other information in the upper - XYZ - area in the header of the file.
![html iframe source code not accessible html iframe source code not accessible](https://i.stack.imgur.com/X4sgJ.png)
We would like to present the components in a Bootstrap-like documentation.
![html iframe source code not accessible html iframe source code not accessible](https://forum-files-playcanvas-com.s3.dualstack.eu-west-1.amazonaws.com/original/2X/1/133d9788b1cb08e5b42170e61d4b1b0dbe151641.png)
For this we create a separate CSS & JS file for each theme. We have a project to create frontend components built with SCSS and TS.