We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For each of model page aliases (if exists) we should generate html pages like this:
<html> <head> <title>Page title</title> <META http-equiv="refresh" content="0;URL=/some/bem-info/url"> </head> <body></body> </html>
The text was updated successfully, but these errors were encountered:
Its better to generate nginx configs with redirects instead of html pages with client side redirects.
Sorry, something went wrong.
@vithar it's not quite so because there's no way to use user nginx config at gh-pages
We need proper redirects in production, not in development (e.g. gh-pages)
Is there any reason not to use gh-pages as production?
No branches or pull requests
For each of model page aliases (if exists) we should generate
html pages like this:
The text was updated successfully, but these errors were encountered: