Custom Pipelines
Importing Gulp Tasks
You don't have to use our gulp pipeline, just import the task into your own gulpfile
You can fork this example project to see an example of how to import Fomantic UI tasks into your project.
Semantic.json Settings
Auto-Install
Running npx gulp install
normally will launch an interactive installer, to allow this installer to run without user interaction and use all settings from your semantic.json instead, include a special flag autoInstall: true
in your semantic.json
file.
Right-to-left (RTL) Languages
Including the flag rtl:true
will build Fomantic UI using RTLCSS.
To build both LTR and RTL versions use the flag rtl: 'both'
Prototyping with Fomantic UI
Sketch Files
If you are looking to prototype layouts using Sketch with Fomantic UI check out Semantic UI Sketch Files
Single Components
Tagged Releases
Component repos are released on NPM and as tagged releases on GitHub.
Check the list of repos available under fomantic on GitHub
Each component's release notes will automatically update with the relevant notes for that component from the main release.
Server-Side Rendering
Individual components repos include an auto-generated index.js
file to simplify require
use with NodeJS, for server-side rendering or with Browserify.
Importing LESS
LESS Only Distribution
A special distribution Fomantic-UI-LESS is available for projects that use custom integrations and do not require our build tools.
Importing Semantic
semantic.less
is available in all releases as an entry point for importing multiple components from other LESS files.
Importing Components
If you need to import individual components, you should scope each import to avoid inheritance issues.
Running Docs Locally
Download Docs Server
The easiest way to get Fomantic UI docs is to clone the repo
Install Dependencies
Fomantic UI's documentation is written in Docpad an amazing static site generator built in NodeJS
A Note About Paths
Fomantic UI's build tools include two special commands build-docs
and serve-docs
for use with the documentation. These will pass changes from the ui/ folder directly to a live docs server.
These gulp tasks expect two sibling folders
Build UI
The first time you run docs you will need to build the whole project once
Run Docpad Server
Docpad
Serve UI to Docs
You can then continue to make modifications to UI and "serve" these files to a live docs instance to see your changes immediately
Hosted Docs
If you are managing your documentation you can automatically deploy to GitHub Pages using a built in docpad gh-pages plugin
For more information about GitHub Pages, check out the docs on GitHub
Custom Docs Paths
Doc task paths are specified in a file tasks/config/docs.js
and can be adjusted to use any folder set-up necessary for your project.