Ok, I see the point of having shorter lines, but I think that we still should try to maintain a consistent page width. Maybe we can do so by moving to a 2-column layout or by just making the font size bigger (the current default size is pretty small for my eyes anyway ...)?

On 9 Jun 2015, at 18:21, Ian Maxon wrote:

It's on purpose. For big long stretches of text, it makes it really hard to read if the text takes up the whole width of the page. For bigger text with
graphics though it's not much of an issue.

On Sun, Jun 7, 2015 at 6:19 PM, Till Westmann <[email protected]> wrote:

I generally like the stylesheet, but I think that we still have some
layout challenges.
The width of the individual pages is not consistent and that doesn’t look
nice switching between “tabs”.
Do you know why that happens?

Cheers,
Till

On Jun 4, 2015, at 7:44 PM, Ian Maxon <[email protected]> wrote:

Hey everyone,

I've been working on making a better website to use for our Apache
domain.
You can check out a preview here :
*https://parshimers.github.io/asterix-website/
<https://parshimers.github.io/asterix-website/>* , and the source is
here :
https://github.com/parshimers/asterix-website . It should build like any
other Jekyll website, just be sure to change the URL if you try
previewing
it locally.

Any thoughts would be welcomed. I think the frontpage still needs some
work
(the features should have some sort of small image to illustrate each one ), and there should be a detailed features page. The documentation also needs to be harmonized and integrated with this site. I think we could
also
add a blog easily, but I'm not sure how everyone feels about that. It
would
be good to show activity and give people a peek of what's going on
between
releases.

This new website should also be a lot easier to maintain and add content
to
for everyone. There's really not much HTML required unless it is a more complex layout like the front page, for example all of the contribution
pages are just markdown.

Thanks, and looking forward to your comments,
- Ian


Reply via email to