New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rebuild the site infrastructure #27

Open
ndw opened this Issue Oct 22, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@ndw
Member

ndw commented Oct 22, 2018

Using Jekyll was both convenient and simple. And it does have some nice features in terms of ease of publication. However, it's a mess from a markup perspective, which seems a little counter-productive for this project.

I propose to rebuild the site using Gradle as the driving build technology. It's well established so there's likely to be other members of the community that know about it, it's JVM based so it's cross-platform, and it's commonly available in CI environments.

Goals:

  1. The source files for pages in the website should be in markup (I propose HTML, or Markdown, or DocBook to start. DocBook is probably overkill, but it will demonstrate using XML.)
  2. The organization of the source documents should have an obvious correspondence to the organization of the published pages.
  3. We must preserve automated publication through PRs, with appropriate validation

@ndw ndw self-assigned this Oct 22, 2018

@btusdin

This comment has been minimized.

Collaborator

btusdin commented Oct 22, 2018

@ndw

This comment has been minimized.

Member

ndw commented Oct 22, 2018

You shouldn't have to do anything but edit the pages and make PRs. If you want to run the system locally, you should be able to run "./gradlew website" and it should all just magically work. There's a lot of reason to be optimistic that this will be the case.

@ndw

This comment has been minimized.

Member

ndw commented Oct 22, 2018

(It won't be the case, because these are computers, but I have boundless optimism.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment