Regarding the routing error, it does appear to be because the Router wasn't the root Component
I refactored my code so that the Containers wrap the Components with the ThemeProvider and it worked like a charm
https://github.com/cssnano/cssnano/blob/master/site/src/layouts/Guide/index.js
http://cssnano.co/ then navigating to 'Guides'
http://cssnano.co/ then navigating to 'Guides'
loading it directly from the url works fine.
What version of phenomic are you using?
Hello 👋🏻, I would like use some .GPX file as content and map over each file to create pages. Do I need to use the
plugin-transformer-markdown, the plugin-transformer-json or a special transformer ? Could I find an exemple somewhere ? I found the "toto" in the docs https://phenomic.io/en/packages/plugin-transform-markdown/docs/
In the https://github.com/phenomic/phenomic/releases/tag/v1.0.0-beta.2 release, you spoke about the unified plugins but I could not find how to use them
GPX file are XML file
Maybe I will try to create a plugin-transformer-xml
I need to upgrade to webpack 4, I heard that this migth help
(to avoid old uglify)
For my site I’ve created a custom component to embed a YouTube video. I am using a components map as shown in react-app-markdown-with-custom-components. I've noticed that adjacent components don’t get rendered. For example:
<video id=“some-id” />
<video id=“some-other-id” />only the first video gets rendered. Whereas this does work:
<div>
<video id=“some-id” />
</div>
<div>
<video id=“some-other-id” />
</div>Any tips?
@ArthurClemens probably an issue with the parser
Is this better with
<video ></video><video></video>? (not self closing tags)?
Thank you!
Hello. I am trying to get coloration on my code blocks. I see that
remark-highlights is used. I specified the language for each of my code blocks (put javascript after the 3 markdown backticks to open the block), but I don't get any colors. I also installed language-javascript package, in case it was needed, but still nothing. Do I miss something ?
For example, I want to add
babel-plugin-styled-components
The only thing I could thing of that might work is create my own version of
plugin-bundler-webpack with a one-line-change to add babel-plugin-styled-components to the babel plugins. Then I'd have to create my own phenomic preset which uses my plugin-bundler-webpack instead of the default one
I figured that was a bit much to change one bit of config so I wanted to ask first
@tleef For now you can do that via a custom webpack config that inherit the default one. Example here https://github.com/MoOx/maxim-hylian.fr/blob/master/webpack.config.js
@MoOx I want to ask if you need any help getting to v1. You are so close but its been a while without any new commits. Is there something blocking?
Of f the top of my head the only major improvement I can see is continuity between the compiled and debug versions of the site. I've had problems with differences in both directions. Things working in the debug version that don't work once compiled and things working in the compiled version that don't work when using the debug server.
When something doesn't work in the compiled version its generally just an issue with server side rendering. Not too tough to figure out. On the other hand. I've been running into issues with styled-components where sometimes they don't load the css in the debug version but always work as expected with the compiled version.
In addition to the proposal you make (that I have in mind already, and that should not be that hard to handle), I want to replace current database engine with some sql generated tables for better performance (hot loading can be currently pretty slow). I have started a wip and will continue on it as soon as I have enough mental strenght
Meanwhile if you want to work on something, feel free to open issue, and I can try to lead you from there :)