Skip to content
Branch: master
Find file History
kwridan Updating manifest documentation (#359)
- Scheme section no longer appears in block quotes
- Updating scheme generation note
Latest commit d32dcf0 May 18, 2019
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
contribution Add Docz Apr 22, 2019
public Use dark code highlighting Apr 22, 2019
usage Updating manifest documentation (#359) May 18, 2019
.gitignore Add Docz Apr 22, 2019
README.md Document the manifest models (#267) Mar 9, 2019
doczrc.js Use component for project attributes May 17, 2019
package.json Use component for project attributes May 17, 2019
yarn.lock Use component for project attributes May 17, 2019

README.md

Documentation

For users πŸ‘©β€πŸ’»

If Tuist caught your attention and you'd like to explore it further, the following resources will help you configure and get the most out of the tool:

  • Getting started: Learn how to install the tool on your environment and generate your first project.
  • Manifest files: Projects are defined in manifest files. This page describes all the attributes that are available.
  • Dependencies: Learn how to define dependencies between targets and with pre-compiled libraries and frameworks.
  • Setup: Learn about the up command which handles the configuration of the environment for your projects to run.
  • Managing versions: It dives into how Tuist ensures rep
  • Frequently asked questions: Find answers for the most commonly asked questions.

For contributors/maintainers πŸ“š

The following list contains all the documentation for people that are interested in contributed to the project. They get updated as the project evolves so even if you are already a contributor, we'd recommend you to revisit them once in a while:

  • Getting started as a contributor: Are you new to contributing to the project? You'll find some recommendations to start from.
  • Code of conduct: Needless to say, you should be a nice developer, have a good conduct and reject any unacceptable behavior from you or any member of the project.
  • Changelog guidelines - Changes to the project are reflected in the project CHANGELOG.md file. This document contains some guidelines the file adheres to.
  • Core team: The Tuist Core team is a group of contributors that have demonstrated a lasting enthusiasm for the project and community. You can read more about their responsibilities and get to know the team.
  • Zen principles: A set of principles on which maintainers and contributors base their decisions.
You can’t perform that action at this time.