[WIP] New Website #3
Conversation
|
I would prefer to change the blue in the menu to the same red as the logo. Apart from that, the design looks nice imo :) |
index.html
Outdated
|
great, thanks! i only have a few questions for the header:
|
|
Started to refactor for Jeckyll - I was playing with the idea of using my PHPCR web framework, Slinp (https://github.com/dantleech/slinp), for the website, but finally decided against it. It is better to use a static site in this case. One thing that might have been possible with a scripted page would have been a page which allowed users to see the features supported by each implementation (by reading the repositories descriptors) - but I guess we could generate this, or just maintain the tables manually. |
|
jekyll can be somewhat limited, but will be simple to maintain on this infrastructure, so +1 for sticking with that. thanks dan, looking forward to the new site. |
|
Updated again, the outline of the whole website as I see it is there now. Need to transplant some tutorials into it and add some more content. Will post a demo soon. |
|
ok heres the current WIP: http://phpcrwebsite.dantleech.com |
documentation/index.md
Outdated
There was a problem hiding this comment.
i think one title "Reference" would be enough, and then have first API Reference and then add the sql2 reference once we have it.
documentation/index.md
Outdated
There was a problem hiding this comment.
Tools? and list the marmelab browser as well? i know that you also have a tools page, but i think that is ok. or we could just link to the tools page from here to avoid reduncancy.
|
we might also move https://github.com/phpcr/phpcr#port-status somewhere into this page (with a different title like "JCR and PHPCR") |
|
Updated again, removed the @todos and linked to slides and imported the "PHPCR Tutorial" from |
documentation/index.md
Outdated
There was a problem hiding this comment.
Are there other slides (ither than those mentioned above)?
There was a problem hiding this comment.
not that i know of. the credits for the intro slides should go to lukas as well, he did work on that too. and the filename should be intro.html or something.
There was a problem hiding this comment.
I don't see any intro.html file ..
There was a problem hiding this comment.
I mean: we should rename the presentation filename from "slides" to "phpcr-intro".
----- Reply message -----
Von: "dantleech" notifications@github.com
An: "phpcr/phpcr.github.io" phpcr.github.io@noreply.github.com
Cc: "David Buchmann" david@liip.ch
Betreff: [phpcr.github.io] [WIP] New Website (#3)
Datum: Fr., Mai. 30, 2014 15:10
In documentation/index.md:
+layout: default
+title: Documentation
+---
+### Tutorials+- General Tutorial
+- Integrating with Symfony+### Reference
+- API Reference
+### Slides
+- PHPCR Introduction by David Buchmann
+- PHPCR, Une Introduction by Daniel Leech (in French)
I don't see any intro.html file ..
—
Reply to this email directly or view it on GitHub.
|
Added a "news" section |
|
imho once the site is decently useable on mobile devices we should merge. no need to try and cover everything in this PR |
|
ok, it should be responsive now ... I have to go now so cannot verify, but have updated the site |
There was a problem hiding this comment.
can we depend on phpcr-docs and pull this file in in the Makefile? having a copy of the tutorial is going to make them diverge fast.
There was a problem hiding this comment.
ah, or in the jekyll build instructions, if we can control that at all...
There was a problem hiding this comment.
i was thinking more of deprecating the phpcr-docs and having all the docs on the website, its easier to manage I think (and we can take advantage of jekyll features like syntax highlighting). Otherwise we would have to find a way serve the phpcr-docs independently and integrate them into this site.
|
I would vote against making the "news" section the home page. we won't have many news and then it will look weird. the main reason for this site imho is to point people not knowing about phpcr there so they can find out about it. |
|
I think the news should be on the front page -- its a way of informing visitors about PHPCR news who are there for other reasons (e.g. looking at documentation). I think there could be regularish news, e.g. when PHPCR is talked about at conferences, new tools (phpcr-shell, phpcr browser) and updates for those tools, user stories, new implementations (e.g. OAK) etc. There is a risk it could make the project look dead if it is not maintained, but if it is maintained it makes the project look alive, which encourages people :) |
|
Renamed the PHPCR-tutorial to "PHPCR Guide" and added syntax highlighting. |
|
Cool. Can you please do a Pr on phpcr-docs to replace the tutorial contnet with a link to where the guide will be online? ----- Reply message ----- — |
|
Okay, lets go with news for front and we each schedule us a monthly reminder to check if there is news. If we have no news for 2 months we switch to about (and back to news when we have new news). Deal? Do you squash and merge? |
- New website using Jekyll - New logo (or rather, we have a logo!) - Imported PHPCR tutorial from phpcr-docs
|
Sounds good, I have squashed .. |
|
I have merged... |
See online demo:
http://phpcrwebsite.dantleech.com