Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rdf4j-dev] new website progress
Slight change of plans.

It turns out using default Eclipse infrastructure and using the rdf4j.eclipse.org domain is trickier than I assumed. So, for now, I'll just do a swap on our existing infrastructure: I'll take the old wordpress site and the old ascidoc doc site offline soon, and replace both with the new Hugo site. 

Jeen

On Wed, Apr 17, 2019 at 11:34 PM Bart Hanssens (BOSA) <bart.hanssens@xxxxxxxxxxxx> wrote:

Hi Jeen,

 


Nice work.

I assume you also got the Eclipse bulk mail asking projects to move old releases to the archive instead of keeping them on the main sftp location ?

So this might be a good time to shuffle some files around, if necessary.

Enjoy the holidays

 

Bart

 

From: rdf4j-dev-bounces@xxxxxxxxxxx <rdf4j-dev-bounces@xxxxxxxxxxx> On Behalf Of Jeen Broekstra
Sent: woensdag 17 april 2019 2:28
To: rdf4j developer discussions <rdf4j-dev@xxxxxxxxxxx>
Subject: [rdf4j-dev] new website progress

 

Just wanted to give you a quick update on the new website: it's coming along nicely, I have been able to port over most of our existing documentation to Hugo Markdown without significant issues.

 

The plan for rollout is as follows:

 

1. Once I've finalized the content of the hugo site, I'll ask Eclipse webmaster to help us set up hosting at rdf4j.eclipse.org (this currently redirects to rdf4j.org but we'll repurpose it for a running the two sites in parallel while we test things). The idea is that on our end we just have a Jenkins job that deploys the site, and all hosting management is handled by the webmaster team.

2. I'll also ask them to set up a https certificate. 

3. Once we're satisfied the new site is good to go, I'll ask to have rdf4j.org redirect to rdf4j.eclipse.org, and docs.rdf4j.org to rdf4j.eclipse.org/documentation . We can then decommission the old site.

 

Note that the outcome of this will be that our "canonical web address" becomes https://rdf4j.eclipse.org/ instead of just http://rdf4j.org/ .

 

Part of testing is also that I want to see that we can do redirects from old deep links as much as possible. The documentation has been restructured a little bit so it won't be possible 100%, but I'd like some of the obvious entry points to be covered by a smart redirect, at least.

 

Also, one editorial thing: I'm playing with the capitalization of the project name, we have not been very consistent with that in the past I feel. I'm currently in favor of the following defaults:

 

 - "Eclipse rdf4j" (lowercase for rdf4j to align with the logo).

 - "rdf4j"

 - "rdf4j server" / "rdf4j workbench"  / "rdf4j console"

 - When starting a sentence with the short name, capitalize: "Rdf4j is a ...."

 

This is just really nitpicky stuff but I think it looks more pleasant and more recognizable than all caps "RDF4J".

 

Ideally, I'd like the new website to be live somewhere in the first week of May.

 

I'll be offline for a few days for Easter holidays. So a slightly early Happy Easter everyone!

 

Cheers,

 

Jeen 

 

_______________________________________________
rdf4j-dev mailing list
rdf4j-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rdf4j-dev

Back to the top