Website Update Plan

[inkydragon]

The Aegisub software itself has an upgrade plan: Release new stable (3.4.0) · Issue #214 · Aegisub/Aegisub.

So do the AegSite.

• Set up AegSite using git pages. Aegisub#211
  https://aeg-dev.github.io/AegiSite/
  At least, we need an online website.
• Update or switch to a new static site generator framework.
  —— We choose Hugo.
  And now it's middleman powered by ruby.
  Top Open Source SSGs
• i18n
  Chinese translation: AegDoc-CN
• Update docs. TT-Aeg#42

[inkydragon]

Those docs are actually in wiki format. wiki_link.rb did some hacks to handle wiki link in Markdown format.

Now it's broken, I've already tried to fix this script in one weekend.
However, if we decide to use only the Markdown format in the future, we could simply convert the wiki format to the Markdown
format and remove this dependency.

@CoffeeFlux Should we keep those wiki links? Or just convert all of them into Markdown.

[CoffeeFlux]

I have no issue with converting everything over. I think the site is very difficult to maintain as-is, and any improvement on that front will almost certainly be merged.

I have hosting and can redirect the domain name to that as necessary, so don't worry about that. I just need a way to actually build the site without using a decade-old debian container.

[inkydragon]

It seems like those code generate the TOC. And now it's broken. I don't think we should do it by ourselves.

aegisite/lib/toc_reader.rb

Lines 4 to 5 in 8dfbd70

	module TocReader
	class Kramdown::Parser::TocReader < Kramdown::Parser::Kramdown

aegisite/source/layouts/api.haml

Line 7 in 8dfbd70

- _, toc = Kramdown::Parser::TocReader.parse(template_data_for_file(current_page.source_file), {})

Some new idea: switch to new SSG (Static Site Generators).

• Hugo + doks (theme)
• jekyll + jekyll-rtd-theme

Perhaps we should specify a few features, so that we can compare different SSGs and then select the right one from them.

• Major development languages
• Customizability and extensibility
• Dependencies required for local builds
• Internationalization Support
• Development activity
• ...

[CoffeeFlux]

I've used both Hugo and Jekyll and like them both, with a mild preference towards Hugo. 2021年5月29日(土) 12:26 woclass ***@***.***>:

…

It seems like those code generate the TOC. And now it's broken. I don't think we should do it by ourselves. https://github.com/Aegisub/aegisite/blob/8dfbd70f89940bf8e327dac80c627b948cb0241c/lib/toc_reader.rb#L4-L5 https://github.com/Aegisub/aegisite/blob/8dfbd70f89940bf8e327dac80c627b948cb0241c/source/layouts/api.haml#L7 Some new idea: switch to new SSG (Static Site Generators). - Hugo + doks (theme) <https://getdoks.org/> - jekyll + jekyll-rtd-theme <https://jekyll-rtd-theme.rundocs.io/> Perhaps we should specify a few features, so that we can compare different SSGs and then select the right one from them. - Major development languages - Customizability and extensibility - Dependencies required for local builds - Internationalization Support - Development activity - ... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYIODSDN5MLQR37SSRP4R3TQEIR7ANCNFSM442YU6CA> .

[inkydragon]

Some progress: https://aeg-dev.github.io/AegiSite/

[seproDev]

The website is now available again at https://aegisub.org/. There are still some things needing to be fixed, but that shouldn't take too long.

@inkydragon Could you redirect or disable aeg-dev.github.io/AegiSite? It is the first Google result for Aegisub docs.

[inkydragon]

@seproDev I would like to do some redirects.

With meta refresh

• https://aeg-dev.github.io/AegiSite/ => https://aegisub.org/
• https://aeg-dev.github.io/AegiSite/** => https://aegisite.vercel.app/**
  eg: https://aeg-dev.github.io/AegiSite/docs

[seproDev]

You can redirect both sites to aegisub.org. Currently, links lead to aegisite.vercel.app due to canonical URLs still being enabled. This will be changed with #28

If you want to maintain compatibility with docs URLs you may also want to redirect /3.2/ to /latest/
As we decided to retain the legacy docs at the old path:

• Latest: https://aegisub.org/docs/latest/main_page/
• 3.2: https://aegisub.org/docs/3.2/Main_Page/

[inkydragon]

@seproDev done!

test links:

• main page: https://aeg-dev.github.io/AegiSite/
• doc: https://aeg-dev.github.io/AegiSite/docs/
• doc 3.2: https://aeg-dev.github.io/AegiSite/docs/3.2/
• downloads: https://aeg-dev.github.io/AegiSite/downloads/
• blog: https://aeg-dev.github.io/AegiSite/blog/

[seproDev]

Looks good. Thank you!