Skip to content
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

Update website #578

Open
5 of 9 tasks
futagoza opened this issue Sep 6, 2018 · 8 comments
Open
5 of 9 tasks

Update website #578

futagoza opened this issue Sep 6, 2018 · 8 comments
Labels

Comments

@futagoza
Copy link
Member

futagoza commented Sep 6, 2018

  • move the website into the main repo
  • add the test suites to the website so I can do automated browser testing
  • migrate to a static site generator
  • set up https://next.pegjs.org/ for development of the new website
  • add a custom theme, any required config files, etc for generator
  • move current site pages to docs
  • add a new online editor (IE support will not be a priority)
  • update docs
  • when 0.11 is released, move the site to https://pegjs.org/
@futagoza futagoza mentioned this issue Sep 18, 2018
29 tasks
@futagoza futagoza added the task label Dec 22, 2018
@futagoza
Copy link
Member Author

Decided to:

  • Use VuePress as the static site generator
  • Move to Now v2
  • Not focus on IE support for the online editor's "Download parser" button

@reverofevil
Copy link

Yay, what a win!

@futagoza
Copy link
Member Author

win?

@reverofevil
Copy link

Yes, a win. As if you played a game for years and won a grand prize.

@mikeaustin
Copy link

I was curios about how to run the current web site locally–I wanted to play around with how jsDump outputs objects. If I go into website and do npm install, npm start, I get:

Error: Cannot find module '@pegjs/bundle-generator'

@futagoza
Copy link
Member Author

The website folder is there for easier to access reference while I rebuild the site in VuePress, and hasn't been updated for a while.

@StoneCypher
Copy link

The marked complete URL doesn't exist, and this is about a two hour job with github pages. There's no difficulty in supporting IE; I don't know why you keep saying that. I'm really worried that there's a bunch of portability timebombs in 0.11.0

I'm not really sure, but it looks like the zeit account attached might be gone

Let's stop using exotic tools and switch to standard stuff that will stay up please

@StoneCypher
Copy link

Also, I found what appears to be an unrelated copy of the same build, and it appears to be identical to the one in production

This suggests that any IE support problems are about damage to the engine, and are unrelated to the site

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants