Move forward

[adrientetar]

We still have a few steps to go before we get fully migrated and visible to the users.

• Upgrade the website backend, cleanup the code
• Cleanup empty pages, migrate/cleanup and update existing data, i.e. make it concise and functional
• also remove the robots restriction
• Shut down the old website, eventually with a redirect (in progress)
• Remove outdated in-tree documentation in fontforge/fontforge
• Release a new version, with proper binaries
• Make binaries one-click accessible from the website (typical, self-documenting installers)
• implement OS detection
• Update Wikipedia articles

[davelab6]

So, I am worried that not all the info in the old site (in the codebase
under htdocs) is in this one.

I also think we should remove the subdirectories and keep the old URLs as
much at possible.

Shut down the old website, eventually with a redirect (that one is not for me)

Toby Thain is quick to point the DNS when ready
On 17 Jul 2014 15:45, "Adrien Tétar" [email protected] wrote:

We still have a few steps to go before we get fully migrated and visible
to the users.

• Upgrade the website backend, cleanup the code
• Cleanup empty pages, migrate/cleanup and update existing data, i.e.
  make it concise and functional — also remove the robots restriction (←done)
• Shut down the old website, eventually with a redirect (that one is
  not for me)
• Remove outdated in-tree documentation in fontforge/fontforge
• Release a new version, with proper binaries one-click accessible
  from the website (not for me either) — implement OS detection (←done)

—
Reply to this email directly or view it on GitHub
https://github.com/fontforge/fontforge.github.com/issues/25.

[adrientetar]

I'm not sure I will update the existing documentation since it's a lot of work but I will try to have it clean and working on the website.

[davelab6]

Yep no need to update it to launch I think, just don't want to lose anythign

[adrientetar]

@davelab6 Can you access the old site to put up banner indicating the new site? Lots of people are completely unaware of the new development. If I was to edit the stylesheet could you put the edits on the old website too?

[davelab6]

I think I have FTP details somewhere, yes. New index.html file?

On 21 August 2014 11:26, Adrien Tétar [email protected] wrote:

@davelab6 https://github.com/davelab6 Can you access the old site to
put up banner indicating the new site? Lots of people are completely
unaware of the new development. If I was to edit the stylesheet could you
put the edits on the old website too?

—
Reply to this email directly or view it on GitHub
https://github.com/fontforge/fontforge.github.com/issues/25#issuecomment-52953313
.

Cheers
Dave

[adrientetar]

Or just edit it to add this right under the body tag:

<div style="height: 1.5em; padding: 0.25em; background: red; color:yellow; text-align:center; font-size:1.4em">
    <a href="http://fontforge.github.io/" style="color: yellow">DEPRECATED: New website on GitHub at fontforge.github.io.</a>
</div>

[simi]

Will be PR where all links to sourceforge will be migrated to github (where possible) welcomed?

I started to migrate http://fontforge.github.io/en-US/documentation/utilities/ when I realized those links are mentioned at another pages as well.

[adrientetar]

Dropping links to sourceforge is part of the deal, the endgoal being so remove it completely. Please go ahead if you want to send PRs to improve the situation.

[adrientetar]

@davelab6: ping, can you do the change to the old website?

[davelab6]

@adrientetar done :) @simi see PR :)

[larsenwork]

Trying to make the structure a bit more flat + general cleanup: https://github.com/fontforge/fontforge.github.io/tree/flat-structure