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

Website is not updating #436

Closed
michaelpj opened this issue Jan 17, 2023 · 4 comments · Fixed by #438
Closed

Website is not updating #436

michaelpj opened this issue Jan 17, 2023 · 4 comments · Fixed by #438

Comments

@michaelpj
Copy link
Contributor

michaelpj commented Jan 17, 2023

The website doesn't seem to have updated recently, e.g. the new CIP-001 is not present there.

@rphair
Copy link
Collaborator

rphair commented Jan 17, 2023

thanks @michaelpj - we've just been talking about that. @KtorZ is more intimately connected with this but publicly we're facing a huge update in #389 before replacing the ad hoc scripts that built cips.cardano.org with something robust & maintainable that will reflect the new preamble & outline structure.

I missed it the first few times I read the OP for that issue myself, but it clearly indicates that this overhaul of CIPs themselves is a prerequisite for getting that web site working again. If we can't get the manpower for that whole effort between CIP editors & CF itself then I might submit a proposal in Fund10 for one or both of those things.

@michaelpj
Copy link
Contributor Author

I'm a little confused. Would it be hard to support the union of the old and new metadata in the site builder while things transition? Blocking the website on updating all the old CIPs seems like a mistake to me. At the moment people can't even see the new CIP-001 without looking in the source!

@KtorZ
Copy link
Member

KtorZ commented Jan 17, 2023

I'm a little confused. Would it be hard to support the union of the old and new metadata in the site builder while things transition?

No it wouldn't. There's simply no one who's bothered doing it. I was hoping that tackling #389 would be faster but it's bit dragging for a while now.

@KtorZ
Copy link
Member

KtorZ commented Jan 17, 2023

I'll bother. Give me few minutes.

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

Successfully merging a pull request may close this issue.

3 participants