Redesign proposals for the Trisquel website


Sign the work with a free GPL-compatible license.

This my first version was made inspired by the work of the Ubuntu + Mint + Debian community, we can still improve. But I present a proposal of colors, navigation and information.

SVG File - Author: Valessio Brito - License: GPLv3 -

mockup-front.jpg513.46 KB
Sáb, 05/04/2019 - 00:32
Lun, 05/06/2019 - 19:00

Thanks Valessio. I'll reiterate here the suggestions I've made on #trisquel-dev and add some new ones.

- Make everything work without JavaScript.
- Make the Wiki easier to navigate for users with a sidebar and anchor links. See Lilypond's documentation[1] as a possible model.
- Manage the Wiki with git, so that contributors can work offline and merge their changes when ready.
- Potentially organize support forums by topic (see Hyperbola[2] as an example) and structure the documentation around the same topics. The web interface could guide people to the documentation if their question is already addressed, or guide them to the appropriate forum if it is not. Because the forum structure will mirror the documentation structure, it will be easy to add the content of the answer to the appropriate location in the documentation so that the question does not need to be answered again.
- Maintain synchronization between forums and mailing lists.
- Use markdown instead of html in the forums so that it translates better to the mailing list.
- Fix the issue whereby attachments do not get appropriately mirrored between the forum and mailing list.


Mar, 05/07/2019 - 00:56

Hello, valessio.
I am interested in this discussion though I am not going to be into too deep.

As the title and chaosmonk's post show, it seems to be a proposal for a new design of the website.
But what does the design team mean? Are we supposed to submit one concrete comprehensive plan to the project team?

If let me proceed with this discussion with it, I would like to suggest that making it extremely feminine.

Briefly, we can say the majority of design everywhere were ruled by manly things in my opinion. We can only see pure feminine design in a cosmetic counter or a female cloths shop or somewhere.
It is difficult to find a pink fridge or a pink compressor, a pink laptop, a pink computer virus etc. Even Apple products seem to be unisex.
I am a bit reluctant to say this kind of ideology, though. This is just a proposal.

I am going to post a rough sketch but unfortunately I don't know how to sign the licenses to my works yet so I am not sure.

Or rather, honestly I am interested in asking you guys your opinions, since especially you seem to be an experienced artist, about e.g. copyleft matters for especially young people who desire to live as artists and actual situations about it etc, sorry. Of course I would respect your suggestion, though. Just a thought.

How about making an independent Arm or RISK-V website like Arch Linux Arm by pink color as a key tone?

Dom, 05/19/2019 - 01:30

I'm curious to see your contribution. You can make and put in the SVG header or file the type of license. You can also mention it during your posting. I believe that this will be respected.

> I am going to post a rough sketch but unfortunately I don't know how to sign the licenses to my works yet so I am not sure.

I make my collaborations available on a GPL-compliant license or a CreativeCommons (attribution). You should choose the license that best gives freedom to your proposal within the project, in this case, I suggest making it available as GPLv3.


Lun, 09/09/2019 - 20:36

About making Wiki navigation and documentation easier, do you think restructuring the way it's being organized works?

I'm drawing[1]/thinking a structure to reformat focused on user experience.


I'm curious to hear more suggestions/opinions.

Mar, 09/10/2019 - 19:48


I'm a little confused by this. Are the nodes on this graph supposed to be clickable?

I do think we should restructure the documentation.[1] I have set aside writing documentation for now in order to focus on development, but I plan to return to it once all the package helpers are fixed.

Do you think for the new website it would be possible to manage the documentation source as a GitLab project? That would make it much easier to work on collaboratively. I'm currently working locally because the current editing interface is such a mess to work with.


Mar, 09/10/2019 - 21:03

Thanks for remembering this gitlab issue[1], I had forgotten, someone had commented on using website and forum issues, as it is still uncertain if we would use all of gitlab's features.

So the wiki is simpler for non-developers, we need to improve usability and structure. But I agree that some of the documentation needs to be versioned in git and with some integration we can automatically update parts of it on the wiki.