Closed SMakaiTakori closed 1 year ago
Name | Link |
---|---|
Latest commit | 2517ff9d78596986a69002852d091c56a6980e60 |
Latest deploy log | https://app.netlify.com/sites/bloom-guides-template/deploys/64a83ae42f95080008cbc98a |
Deploy Preview | https://deploy-preview-50--bloom-guides-template.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Something changed the styles after the original PR #30 was merged into production yesterday, so
css
was vastly different in production. I am thinking something was missed/altered during merge conflicts, so I am reverting the original PR and reopening the original branch to see if I can figure out why thecss
has been altered.ORIGINAL NOTES from PR #30
Closes #14.
Preview pages
New components
Notes
To keep merge conflicts to a minimum, I'm using the file structure that I noticed web.dev's 11ty instance using:
_includes
.common-tags
package strips out whitespace, ensuring the component renders correctly.I also moved
markdown-it
config to a separate file,markdown.js
, so that we can properly render Markdown within shortcodes. (See this section of the 11ty docs for a description of the problem, and this blog post for more context around the solution here.)