New design, iteration 3

[pieterdd]

Continuing openSUSE/get-o-o#255, I'm working with @ddemaio on the new landing page.

Auto-updating website preview: https://opensuse-landing-demo.netlify.app/

[TobiPeterG]

Hey,
I really love the design, thanks a lot :)

Just nitpicking: IMO openSUSE is not a distro; it's a project offering different distros. :)

[pieterdd]

@TobiPeterG Thank you. The page uses the word 'distro' when talking about individual flavors of openSUSE:

As such, I hope to make it sufficiently clear that openSUSE is a collection of Linux distros.

[pieterdd]

@hellcp I've been talking to @ddemaio about the new website and there were two things you might be able to help with.

First of all, Douglas mentioned that during a team meeting, a preference was expressed for having development/test/production environments for smooth deployment. This would be very easy (and free) to implement with Netlify. I can connect it to a GitHub repo and from that point forward, whenever a push to master happens, Netlify automatically publishes the updated version. I'm currently using it on my fork at https://opensuse-landing-demo.netlify.app/. It's free to use with domain names as well. You just need to configure it in Netlify and your site's DNS. For test server deployments, Netlify can automatically provide deploy previews when a pull request is opened. Would you be open to configuring something like that? I believe there are self-hostable opensource alternatives to Netlify, but that might be too much work for now. However, since you guys have a multiple Jekyll sites it might be useful to have.

Secondly, we're looking to prep the i18n infrastructure integration. I've mirrored the same file structure get-o-o utilizes, being a _data/locales folder containing YAML files with two-letter language codes as filename. As far as I understood, this is not blocking for the initial release, but it would allow translators to contribute localized versions later.

[hellcp]

We already use netlify for get-o-o, news-o-o and quiz, and we don't use our dns there, so I don't know how much it matters to have that

[pieterdd]

Hmm okay. I'm not quite familiar with this type of setup:

;; ANSWER SECTION:
get.opensuse.org.       3600    IN      CNAME   proxy-prg2.opensuse.org.
proxy-prg2.opensuse.org. 2690   IN      A       195.135.223.50

According to whois this is a SUSE IP, not a Netlify IP.

[hellcp]

We use it only for staging and not deployment

[pieterdd]

Ah, that explains a lot. Could you help get this and the i18n infrastructure set up?

[TobiPeterG]

@TobiPeterG Thank you. The page uses the word 'distro' when talking about individual flavors of openSUSE:

As such, I hope to make it sufficiently clear that openSUSE is a collection of Linux distros.

Hey, thank you. :)

It now says: "openSUSE is a free Linux OS for desktops, servers and containers.", which is more or less the same, but this has already been discussed, right?

[pieterdd]

I've altered the wording:

We have to strike a balance between keeping the messaging simple while still accurately representing openSUSE's mission.

[TobiPeterG]

I've altered the wording:

We have to strike a balance between keeping the messaging simple while still accurately representing openSUSE's mission.

This is perfect now in my opinion, thank you so much :)

[hellcp]

I can't do much about i18n and nowadays I don't really know who to reach out to about it. For netlify feel free to reach out in a week or two when I'm not in norway :D

[ddemaio]

The way I understood it from the meeting was that the PO needs a setup in css and /tree/master/po, which will automatically acknowledge the changing of strings through webhooks. It just needs the correct setup. I don't know if there is any dependency to Gulp. I doubt it since other pages without Gulp connect the same way to l10n.o.o. @lkocman can you clarify this?