-
Notifications
You must be signed in to change notification settings - Fork 291
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
docs.perl6.org design #1090
Comments
http://examples.perl6.org/ is a related project and may need the same treatment. |
Indeed an issue has been opened in the examples repo Raku/examples#46 |
Turns out that because of how we build the docs, this isn't a simple cut and paste fix. Working on it now. |
This is kind of blocked by Raku/Pod-To-HTML#23 - it's generating a bunch of invalid HTML which makes it hard to work on the wrapper HTML |
(P.S.: the module on hack already updated with that PR so the docs build uses it) |
That issue has been solved, so I guess this is no longer blocked. Are we still interested in this? |
IMO it'd be nice for them to be themed the same, but not necessarily to have the exact same design/layout, as they have different purposes and can be best fine-tuned for them. Rust lang does it how I'm picturing it: both main site and the The Book have the same minimalistic theme, but their designs are different, to suit different purposes of the sites. So if, say, all of our sites would be using BootStrap 4, they could have their own layouts they need, but they could share a single theme file and so any changes to the theme would propagate to main site, docs, and examples site automatically. That said, I'd say it's a waste of time to try to do that with the current
P.S. in 2-3 months, perl6.org will see an update that'll have it upgraded to BootStrap 4 and the design might change slightly too. |
New site layout is available for review at raku/doc-website - please provide any feedback there. |
It would be nice if the docs have the same design as the main perl6.org website. For consistency.
The text was updated successfully, but these errors were encountered: