Skip to content

Website style guide #5

Open
Open
@rolandlo

Description

@rolandlo

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:

That's a good point to note. The readme/documentation definitely needs to be updated to be more accommodating to end users and non-technical people, since Xournal++ is meant for the everyday user. We also have plans to set up a website, but the entire team has been low on free time recently. :(

So the goal is to create a website that

  • is accommodating to (and easy understandable for) end users and non-technical people

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

  • makes it easy to find information quickly

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

You only have 10 seconds to make an impression on a visitor and to let them know what they’ll get out of visiting your page. If they aren’t impressed within that time, they’ll leave.

So the website ideally also

  • looks visually appealing and gives a visual impression how working with Xournal++ looks like

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

  • has a simple enough design, so that it is easy to contribute

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions