-
Notifications
You must be signed in to change notification settings - Fork 36
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
Website style guide #5
Comments
I think we should add link to this page in main Xournal++ repository (although it is still under construction), because this would inform more people (including contributors) about existence of this site and would speed up its creation. |
@ptiuk I think so, too. Where would you like to link it? In the Readme.md that is displayed on the main page of the repository? Or with a pinned issue? |
I think it should be put in README and in About section. |
It would be good to add buttons to top bar (like on example site), but I don't know how to do it. |
I don't know if the style of the website is still a priority (or even something with minimal relevance), but I recently ended up on this website from the polybar project and I think it is very very good. His style is very clean and the colors remind me of recycled paper or something. What do you think? Note: I know almost nothing on the technical side, so if the suggestion breaks Rolando's last point about the simplicity of the design, just ignore it. |
From the technical side this looks hard to combine with mkdocs. We should stick to mkdocs (and the material theme). |
I think one project that we can take inspiration from is Visual Studio Code |
The website needs screenshots, the README on github has some already! |
@YellowOnion Sure. This will help to achieve the goal
We'll wait until the new icons (PR #2886) are merged though (which should happen soon). |
In this issue I would like to share thoughts and ideas on the style in which we want the website to be. Looking through previous issues on the repository website I found issue #1444 where @Technius indicated the general direction:
So the goal is to create a website that
This means that we should avoid going into too much technical details or at least move those details to specialized sections. Sometimes things need to be simplified a bit. Non-technical people should not need to visit the github pages to find basic infos. I would add, that the website ideally
For this purpose we benefit from the search utility provided by mkdocs and from the clear design with clickable titles and subtitles. That is not enough, though. According to mrnwebdesigns.com
So the website ideally also
For a positive example see how our competitor Openboard.de presents their features. From just the image on the top you already know pretty much how working in Openboard looks like and what it is designed for. An example of a website partially created with mkdocs that has similar visual appeal is the retropie website.
From perspective of creating the website one more point seems important, namely that the website
By using mkdocs as website creator this should not be the most difficult point to achieve.
So these are the four most important points that came to my mind. Do you agree with all of them? What are your ideas about what we should aim for with the website?
The text was updated successfully, but these errors were encountered: