Skip to content
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

Closed
hankache opened this issue Dec 29, 2016 · 9 comments
Closed

docs.perl6.org design #1090

hankache opened this issue Dec 29, 2016 · 9 comments
Assignees
Labels
big Issue consisting of many subissues wishlist "nice to have" issues; might require a lot of work or a big change or be low priority

Comments

@hankache
Copy link
Contributor

It would be nice if the docs have the same design as the main perl6.org website. For consistency.

@coke coke added big Issue consisting of many subissues site wishlist "nice to have" issues; might require a lot of work or a big change or be low priority labels Dec 29, 2016
@coke coke self-assigned this Jan 4, 2017
@gfldex
Copy link
Contributor

gfldex commented Jan 4, 2017

http://examples.perl6.org/ is a related project and may need the same treatment.

@hankache
Copy link
Contributor Author

hankache commented Jan 6, 2017

Indeed an issue has been opened in the examples repo Raku/examples#46

@coke
Copy link
Collaborator

coke commented Feb 1, 2017

Turns out that because of how we build the docs, this isn't a simple cut and paste fix. Working on it now.

@coke
Copy link
Collaborator

coke commented Feb 2, 2017

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

@tisonkun
Copy link
Member

tisonkun commented Nov 4, 2017

@coke

Raku/Pod-To-HTML#26

@zoffixznet
Copy link
Contributor

zoffixznet commented Nov 4, 2017

Raku/Pod-To-HTML#26

(P.S.: the module on hack already updated with that PR so the docs build uses it)

@JJ
Copy link
Contributor

JJ commented Apr 8, 2018

That issue has been solved, so I guess this is no longer blocked. Are we still interested in this?

@zoffixznet
Copy link
Contributor

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 htmlify.p6-based site. A dynamic site that has the docs stored in some database is a higher priority and would annul all the efforts spent into design/markup changes to htmlify.p6-based site.


same design as the main perl6.org website

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.

@coke
Copy link
Collaborator

coke commented Feb 3, 2023

New site layout is available for review at raku/doc-website - please provide any feedback there.

@coke coke closed this as completed Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
big Issue consisting of many subissues wishlist "nice to have" issues; might require a lot of work or a big change or be low priority
Projects
None yet
Development

No branches or pull requests

7 participants