https://github.com/upfluence/oss

A frontend framework for the awesome people from Upfluence (Living Styleguide @ upfluence/oss-components)
https://github.com/upfluence/oss

bootstrap3 brand-assets brand-colors css design-systems frontend-framework less styleguide

Last synced: about 2 months ago
JSON representation

A frontend framework for the awesome people from Upfluence (Living Styleguide @ upfluence/oss-components)

• Host: GitHub
• URL: https://github.com/upfluence/oss
• Owner: upfluence
• Archived: true
• Created: 2017-02-06T14:28:32.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2022-08-03T12:02:00.000Z (over 2 years ago)
• Last Synced: 2024-09-19T11:13:24.538Z (about 2 months ago)
• Topics: bootstrap3, brand-assets, brand-colors, css, design-systems, frontend-framework, less, styleguide
• Language: Less
• Homepage: http://oss-styleguide.upfluence.co
• Size: 1.81 MB
• Stars: 10
• Watchers: 15
• Forks: 2
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • Codeowners: .github/CODEOWNERS

Awesome Lists containing this project

README

        
# OSS (117)

![Mr Bonisseur de La Bath](https://i.imgflip.com/6orln3.jpg)

##  Deprecated and Archived

After discussions with the Upfluence frontend team, this projects has been deprecated and its files have been moved into

the **[upfluence/oss-components](https://github.com/upfluence/oss-components)** project (Pull Request: https://github.com/upfluence/oss-components/pull/200).

There reasons are that we have noticed that the split between this package (holding agnostic, Less CSS + assets only code)

and the @upfluence/oss-components package (holding more Ember-specific code) is not viable anymore and brings some pain

point that are a bit annoying:

- having to open PRs in two projects for the same tasks

- Yarn links w/ @upfluence/oss that are not always straighforward (even more if you link this package to another running app)

- Documentation being split between two packages