You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we don't have any sort of html to test the theme locally. We should consider finding a way to test the changes against a site without having to push the commit. A possible solution is to have an index.html that showcases the theme. However due to the complexities of the website layout it'd be difficult to create a comprehensive test bed without using a full index page from our blog or website. Even then, we'd miss some site-specific use cases.
There may not be a good solution, but I'm hoping my future self (or a contributor) will be able to come up with something.
Official workaround: copy the style.css into the test environment's assets folder (e.g. the blog or website). Once modifications are done, copy the css file back into this project's assets folder, commit, push.
The text was updated successfully, but these errors were encountered:
Currently we don't have any sort of html to test the theme locally. We should consider finding a way to test the changes against a site without having to push the commit. A possible solution is to have an index.html that showcases the theme. However due to the complexities of the website layout it'd be difficult to create a comprehensive test bed without using a full index page from our blog or website. Even then, we'd miss some site-specific use cases.There may not be a good solution, but I'm hoping my future self (or a contributor) will be able to come up with something.Official workaround: copy the style.css into the test environment's assets folder (e.g. the blog or website). Once modifications are done, copy the css file back into this project's assets folder, commit, push.
The text was updated successfully, but these errors were encountered: