-
-
Notifications
You must be signed in to change notification settings - Fork 336
Re-work the presentation of the main page #510
New issue
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
Conversation
* add redirects from old urls * old manuals are now served as stable * and unstable manuals were added * <link rel="cannonical" url=".." /> was added not to confuse search engines
change manual location and add unstable version
As discussed
This *strongly assumes* that the SVG will be available, and also assumes that the DOM and styles are ready to embed the SVG at this location. Additionally, yet unwritten, another component will be needed at the location where the "pane" with the actual demo will be shown. Finally, JavaScript will be used to make the pane show up properly when activated.
Note that this is a manual edit of the template, for testing purposes. This should be made a part of the demo processing tooling.
This reverts commit 27ea2e2.
@garbas the SVG file template is: It is totally expected to see a black file. They end up being embedded as Hopefully you can extrapolate how it works from that document, though here's some notes:
Be careful when continuing to the next line; |
It has been verified that recent iOS versions don't need that anymore.
Though only show with `-debug` body class
This can be used to better document responsive bugs by showing at which level the user saw the issue.
This way we can ensure all usage of the component are coherent with each other.
See, there's absolutely nothing specific to the demo panes! It's a generic behaviour for panes.
Using a BLOCK like this is the only way we will be able to manage having misc. contributors edit the site. No soup of DOM as an internal detail.
This is not entirely complete, there's still action points to do, but they are content action points, which are not part of the work on this PR. |
This is a proposed feature, not implemented yet.
Subject of this PR: only the presentation of the index page. Any other page should see no changes, though if a regression compared to the main PR's state is found, it's a bug.
Note that the text of the main page is not subject of this PR either. I'm working on the implementation only.
TODO
Contents TODO