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

🚀 Introduce v2 #950

Merged
merged 94 commits into from
Jul 18, 2019
Merged

🚀 Introduce v2 #950

merged 94 commits into from
Jul 18, 2019

Conversation

pedronauck
Copy link
Member

@pedronauck pedronauck commented Jul 10, 2019

Features

  • Use Gatsby as the default bundler
  • Remove docz-theme-default package
  • New Docz theme inside gatsby-theme-docz
  • Component shadowing for all theme components
  • Theme-ui integration
  • Adapt config arguments for Gatsby

Documentation

  • Update readme
  • Write migration guide
  • Update website documentation

pedronauck and others added 30 commits May 12, 2019 03:28
@izakfilmalter
Copy link

Is there a way to test this locally?

@pedronauck
Copy link
Member Author

pedronauck commented Jul 12, 2019

Yeah, for sure @izakfilmalter.

Just clone this repository and:

  • git checkout feat/gatsby
  • yarn && yarn packages
  • cd examples/basic
  • yarn dev

@zicodeng
Copy link

Hey @pedronauck nice job on Gatsby integration. Can you elaborate a bit more on what it means to Docz theme contributors? Does V2 mean other Docz users can no longer download other people's theme? Thanks

@draperunner
Copy link

I see you have merged many of the PRs into this branch and closed them. I guess this means v1 is dead and your focus is on releasing v2? Do you have any timeline for this?

I must say I'm a little disappointed that v1 got so few minor and patch releases. Issues like #837, #707 and #882 have been around for a couple of months, with multiple PRs to fix them (#882, #924). And now we have to wait for a new major version with probably a lot of breaking changes? For how long should we expect a major version to be maintained? There's less than a month between v1.0.0 and v1.2.0 (latest). :/

@pedronauck
Copy link
Member Author

@draperunner I'm focused on the v2 now exactly because I think that it will remove a lot of issues related to bundle and will improve a lot the workflow. I'll launch some alpha version soon, very soon.

@pedronauck pedronauck changed the base branch from master to dev July 18, 2019 17:33
@pedronauck pedronauck changed the title 🚀 [WIP] Introduce v2 🚀 Introduce v2 Jul 18, 2019
@pedronauck pedronauck merged commit cfe07b0 into dev Jul 18, 2019
@draperunner
Copy link

Yes, that was very soon indeed. Looking forward to testing it. :)

@samjt
Copy link

samjt commented Oct 4, 2019

when might v2 be deployed to npm?

@draperunner
Copy link

@rakannimer v2 is not far away, is it?

@rakannimer
Copy link
Contributor

when might v2 be deployed to npm?

v2 is already deployed to npm on the next tag, you can try it with :

yarn add docz@next

v2 is not far away, is it?

v2 is very close ! We're tracking it with the 2.0.0 milestone : https://github.com/doczjs/docz/milestone/1

You can follow the progress there and feel free to open issues you think should be solved before v2 official is released !

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.

8 participants