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

Future changes in Geist -- Component System #722

Open
unix opened this issue Feb 8, 2022 · 1 comment
Open

Future changes in Geist -- Component System #722

unix opened this issue Feb 8, 2022 · 1 comment
Assignees
Labels
💬 In discussion Welcome to leave your comments type: documentation Improvements or additions to documentation

Comments

@unix
Copy link
Member

unix commented Feb 8, 2022

Background

Geist is a component library from the community that was created to mimic many of the component libraries from Vercel and retains much of the original style after several iterations.

Geist has been gradually transformed into a component design system after version 2.0, and is being updated with this goal in mind.

(Meanwhile, Geist has not conducted any commercial activities and has not accepted any sponsorship)

More versatile

The goal of Geist should be a generic component system, not a copy of a Vercel design component. The reason for this is, on the one hand, to avoid being misunderstood and, on the other hand, not to limit the future development of the component library.

I think that with the current version of Geist, we or any developer is capable enough to create multiple themes based on the style system, geist should not be limited by a fixed set of themes, but need to find a balance of customization, ease of use, component design.

Plans

Design system

In the next few releases, I will focus more on the development of the design system and allow developers to customize and override more freely.

If possible, document sites should have multiple color schemes, rather than being limited to a particular theme.

Style update

Components that may be misleading or similar in style to the corresponding part are redesigned.

Migration of document sites

Geist's document site has been deployed in Vercel, but because the old organizational plan was discontinued, the next need to migrate to Cloudflare. Require the migration of 5 document sites, and ideally, we can do it within this month.

Others

So, based on this premise, the following kinds of discussions and requests will be closed:

  • Why does Vercel have this component and Geist does not.
  • Why this component style is different.
@unix unix self-assigned this Feb 8, 2022
@unix unix added the type: documentation Improvements or additions to documentation label Feb 8, 2022
@unix unix changed the title Migrate document sites to cloudflare Future changes in Geist Feb 8, 2022
@unix unix pinned this issue Feb 8, 2022
@unix unix added the 💬 In discussion Welcome to leave your comments label Feb 8, 2022
@unix unix changed the title Future changes in Geist Future changes in Geist -- Component System Feb 8, 2022
@unix
Copy link
Member Author

unix commented Feb 10, 2022

Update

  • The documentation site has been migrated to the Netlify platform and is working well. Geist is sponsored by the Netlify Platform Open Source Project, and other open-source documentation (from geist-org) will be deployed on the Netlify in the future.
  • Added link to Netlify in the footer of Geist's documentation page.

Next

  • Within 1-2 weeks we will further optimize the documentation site, including style, usability, loading speed and content updates.
  • All example projects will be updated and organized to ensure that each example project is well described and can be applied correctly to the latest version. (with v2.3.0)
  • Add some examples to make it easier for developers to customize components using the design system.
  • In the next release, all error messages will be organized and more friendly error tips and solutions will be added, which will make it less difficult for developers to use the component system for customization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💬 In discussion Welcome to leave your comments type: documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant