├── README.md ├── code-of-conduct.md └── contributing.md /README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Awesome Fractal [![Awesome](https://awesome.re/badge-flat.svg)](https://awesome.re) 4 | 5 | > A curated list of awesome things related to [Fractal](https://fractal.build/). 6 | 7 | Fractal is a tool for creating powerful component libraries & styleguides that fit the way you work 8 | 9 | ## Contents 10 | 11 | - [Official Resources](#official-resources) 12 | - [Unofficial Resources](#unofficial-resources) 13 | - [Community](#community) 14 | - [Offical Adapters](#official-adapters) 15 | - [Unofficial Adapters](#unofficial-adapters) 16 | - [Mentions of Fractal](#mentions-of-fractal) 17 | - [Showcase](#showcase) 18 | 19 | ### Official Resources 20 | 21 | - [Fractal Website](https://fractal.build/) 22 | - [GitHub Repo](https://github.com/frctl/fractal) 23 | 24 | ### Unofficial Resources 25 | - [Fractal Folder VSCode Extension](https://marketplace.visualstudio.com/items?itemName=baerkins.new-fractal-folder) 26 | 27 | ### Community 28 | 29 | - [Twitter](https://twitter.com/frctl) 30 | - [Discord](https://discord.gg/vuRz4Yx) 31 | 32 | ### Official Adapters 33 | 34 | - [Handlebars](https://github.com/frctl/fractal/tree/main/packages/handlebars) 35 | - [Twig](https://github.com/frctl/fractal/tree/main/packages/twig) 36 | - [Nunjucks](https://github.com/frctl/fractal/tree/main/packages/nunjucks) 37 | - [Mustache](https://github.com/frctl/mustache) 38 | - [React](https://github.com/frctl/fractal/tree/main/packages/react) 39 | 40 | ### Unofficial Adapters 41 | - [Vue](https://github.com/swey/fractal-vue-adapter) 42 | - [React + TypeScript](https://github.com/gtap-dev/fractal-tsx-adapter) 43 | - [Svelte](https://github.com/aredridel/fractal-svelte-adapter) 44 | 45 | ### Mentions Of Fractal 46 | - [Smashing Magazine: Pattern Library First: An Approach For Managing CSS](https://www.smashingmagazine.com/2018/07/pattern-library-first-css) 47 | - [Creative Bloq: Document your design systems with Fractal](https://www.creativebloq.com/how-to/document-your-design-systems-with-fractal) 48 | - [Rachel Andrew: Rebuilding the Perch UI - creating a pattern library](https://rachelandrew.co.uk/archives/2016/05/06/rebuilding-the-perch-ui-creating-a-pattern-library) 49 | 50 | ### Showcase 51 | - [City of Boston](https://patterns.boston.gov) 52 | - [City of Ghent](https://stijlgids.stad.gent) 53 | - [Kanbasu](https://kanbasu.liip.ch/2) 54 | - [Clearleft](http://fractal.clearleft.com) 55 | - [Liip](https://styleguide.liip.ch/) 56 | - [24 Ways](https://bits.24ways.org) 57 | - [Eurostar](https://style.eurostar.com) 58 | - [V&A Museum, London](https://vam-design-guide.surge.sh/) 59 | - [gotoAndPlay](https://play.ee/styleguide/) 60 | - [UCLA](https://webcomponents.ucla.edu/) 61 | 62 | ### Subtheme 63 | - [Mono](https://github.com/AccentDesign/Mono) - Fractal subtheme, built upon the default Mandelbrot theme 64 | - [Nighthawk](https://github.com/gtap-dev/nighthawk) - A custom web UI theme for Fractal, based on Mandelbrot 65 | 66 | ### Starter Project 67 | - [Fractal Atomic](https://github.com/AccentDesign/Fractal-Atomic) - Awesome starter point for your Fractal UI component library based on Atomic Design principles 68 | 69 | > Please don't hesitate to make a PR if you have more resources to share. 70 | 71 | ## License 72 | 73 | [![CC0](https://mirrors.creativecommons.org/presskit/buttons/88x31/svg/cc-zero.svg)](https://creativecommons.org/publicdomain/zero/1.0/) 74 | -------------------------------------------------------------------------------- /code-of-conduct.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at [http://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: http://contributor-covenant.org 74 | [version]: http://contributor-covenant.org/version/1/4/ 75 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | # Contribution Guidelines 2 | 3 | Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms. 4 | 5 | --- 6 | 7 | Ensure your pull request adheres to the following guidelines: 8 | 9 | - Your submission **must be Fractal related** 10 | - Search previous suggestions before making a new one, as yours may be a duplicate. 11 | - Make an individual pull request for each suggestion. 12 | - Use the following format: `[Title](link) - Description.` 13 | - Additions should be added to the bottom of the relevant category. 14 | - Keep descriptions short and simple, but descriptive. 15 | - Start the description with a capital and end with a full stop/period. 16 | - Don't start the description with `A` or `An`. 17 | - Check your spelling and grammar. 18 | - Make sure your text editor is set to remove trailing whitespace. 19 | - The pull request should have a useful title and (if relevant) include a link to the package and why it should be included. 20 | - New categories or improvements to the existing categorization are welcome, but should be done in a separate pull request. 21 | 22 | Thank you for your suggestion! 23 | 24 | ### Updating your PR 25 | 26 | A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. If you're not sure how to do that, [here is a guide](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) on the different ways you can update your PR so that we can merge it. 27 | --------------------------------------------------------------------------------