Skip to content

postcss-preset-env site #178

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

Conversation

romainmenke
Copy link
Member

This is a hard fork. I could not preserve the git history through git patches.

It seems that two separate attempts to create a site where "force" pushed together creating an interleaved git history that can't be re-run easily.


  • The contents of the gh-pages branch have been placed in dist/.
  • The have been no changes to the contents
  • No workspace has been configured yet

I think the next step is to do a one to one port to Astro with minimal changes.
When that is done I can setup the workspace and integrate further into CI.

At the moment I do not want to pollute our package-lock.json or CI with unvetted dependencies.


@nucliweb Is it ok for you to use this branch as a base and open PR's against this one?
postcss-preset-env-site--adaptable-bull-terrier-f20dacef51

Please let me know which flow works best for you.

@romainmenke romainmenke mentioned this pull request Jan 18, 2022
@Antonio-Laguna
Copy link
Member

@romainmenke if that's the case I'm not sure there's too much benefit in keeping this since most of the files will be destroyed/moved around heavily but we can use this in any case :)

@romainmenke
Copy link
Member Author

@nucliweb If you prefer starting from scratch and manually copy/pasting bits from the original repo that is also fine!

Published contents : https://github.com/csstools/postcss-preset-env-www/tree/gh-pages
Current main branch : https://github.com/csstools/postcss-preset-env-www/tree/master

If this is your preference you can let me know and then I will close this pull request.
You can then start your project from the main branch here in a folder : sites/postcss-preset-env

Integrating it further into a mono repo is something we can do after you have a good first proposal :)

@Antonio-Laguna
Copy link
Member

Another option is to provide it in markdown for the time being. Astro can consume markdown so that's also more than valid. Whatever's easier :)

@nucliweb
Copy link

I will create a new markdown file, or files (like modern and legacy), from scratch to use on GitHub repo and with Astro as @Antonio-Laguna comment

@romainmenke
Copy link
Member Author

@nucliweb Sounds good! closing this PR.
Let us know if you need anything :)

@romainmenke romainmenke deleted the postcss-preset-env-site--adaptable-bull-terrier-f20dacef51 branch January 19, 2022 09:12
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 this pull request may close these issues.

3 participants