Building a static Manila site in 2019

Open
#141 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
web-dev

Research direction

Start with the uploaded xmlRpc.root and the Manila setup in the OPML Editor, then reproduce the static-build attempt and the admin URLs on port 5337. Done means a script produces a folder of static files for the 1998 site and the Admin site renders at the documented endpoint.

Written by the indexing model from the issue text.

Description

I'm doing a restoration of the XML-RPC website along with releasing the new JavaScript implementation. I want to get a final clean rendering of the 1998 Manila site, xmlRpc.root.

I have Manila running in the OPML Editor.

I tried writing a script to do the static site build, but I don't have good example code. It would be ideal to just run a script and have a folder of static files appear.

I also tried to get the Admin site to show up. The web server is running on port 5337. I tried this URL:

http://127.0.0.1:5337/admin/ or

http://127.0.0.1:5337/admin/index.wsf

But none produce the admin website.

It's been really interesting, just put in about an hour, and got pretty far.

I've uploaded xmlRpc.root for anyone to have a go at this.

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.