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

[UI] Implementation of Layer5 Design System Website #23

Open
leecalcote opened this issue Aug 23, 2023 · 3 comments
Open

[UI] Implementation of Layer5 Design System Website #23

leecalcote opened this issue Aug 23, 2023 · 3 comments
Assignees
Labels
area/ui User Interface framework/jekyll framework/react help wanted Extra attention is needed kind/enhancement Improvement in current feature kind/epic An issue that describes a set of concerns (issues) language/javascript Javascript related language/markdown

Comments

@leecalcote
Copy link
Member

Current Behavior

Outside of https://layer5.io/brand, no website represents the sistent design system and it's collective artifacts.

Implementation

  1. Select and use static site generator (e.g. Gatsbyjs like layer5.io, Jekyll like many other sites here, or Hugo).
  2. Implement designs from [UX] Website Design for Layer5 Design System #22
  3. Request A record: ux.layer5.io and configuration of CNAME in repo.

Acceptance Tests

  1. Site is publicly available on ux.layer5.io
  2. Maintainers have reviewed and approved site implementation.
  3. Site has GitHub workflow configured to build and publish on PR merge to master branch.

Mockups

See #22


Contributor Guide

@saurabh100ni
Copy link

This issue has been open for some time with no recent activity, unassigning to open it up for new contributors to give it a go.

@hadihaider055
Copy link

@saurabh100ni could you assign it to me, I will implement the new design that I received over slack.

@leecalcote
Copy link
Member Author

Create it on the layer5io/layer5 repo, reusing the existing layer5.io site components, creating new navigational components, if needed. You shouldn't need to do so, but can use the learning paths nav or another existing nav.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ui User Interface framework/jekyll framework/react help wanted Extra attention is needed kind/enhancement Improvement in current feature kind/epic An issue that describes a set of concerns (issues) language/javascript Javascript related language/markdown
Development

No branches or pull requests

5 participants