GitHub Flavored Markdown VS Textile

• Widespread Usage
  GitHub Flavored Markdown (GFM) is widely used in the GitHub community, making it a popular choice for collaborating on open-source projects and documenting code repositories.
• Enhanced Features
  GFM extends the standard Markdown with additional features like tables, strikethrough, and syntax highlighting, allowing for more expressive and informative content.
• Version Control Integration
  GFM is seamlessly integrated with GitHub’s version control system, making it easy to track changes, collaborate on documentation, and propose updates through pull requests.
• Live Preview
  GitHub provides a live preview of Markdown files, which helps users see how their Markdown will render, ensuring the final document looks as expected.
• Cross-Platform Compatibility
  Since GFM is based on Markdown, documents can be easily shared and rendered across different platforms and services, retaining consistent formatting.

Possible disadvantages

• Limited Advanced Formatting
  While GFM offers several enhancements over standard Markdown, it still lacks support for some advanced formatting options found in richer text editors or other markup languages.
• GitHub Dependency
  GFM is primarily designed to work within the GitHub ecosystem, which can limit usefulness outside of GitHub, especially if using features specific to GFM.
• Learning Curve
  Users familiar with standard Markdown might need to learn the additional syntax and features of GFM, which can be an initial barrier for some.
• Consistency Issues
  Rendering consistency might vary when GFM documents are viewed outside of GitHub, as some features might not be supported in other Markdown processors.

• Human-Readable Syntax
  Textile provides a plaintext syntax that is easy to read and write, making it accessible for users who are not familiar with complex markup languages.
• Lightweight
  Being a lightweight markup language, Textile is fast and efficient, allowing for quick parsing and rendering of documents without significant resource consumption.
• Easy Integration
  Textile can be easily integrated into various web applications and content management systems, providing flexibility and adaptability for developers.
• Extensible
  Developers can extend Textile's functionality or customize it to meet specific needs, offering versatility in different development projects.

Possible disadvantages

• Limited Advanced Features
  Textile may lack some advanced features and capabilities found in other more comprehensive markup languages, which can be a limitation for complex document formatting.
• Niche Adoption
  Compared to other markup languages like Markdown, Textile has a smaller user base and community, which can lead to fewer resources, plugins, and updates.
• Learning Curve
  While simpler than some alternatives, new users still need to learn its unique syntax, which may take time and effort, especially if they are accustomed to other markup languages.
• Compatibility Issues
  Not all platforms and tools fully support Textile, which can lead to compatibility issues or require additional configuration and handling by developers.

Demystifying Markdown – Learn GitHub flavored Markdown (GFM) on Skillshare | Clyde D'Souza

Textile Technology Review/Textile Technology - Scope & Salary/Textile Technology colleges

More videos

• Resources for proper putting of code on to GitHub ?

  Not sure quite what you mean. Are you asking "what should I put on GitHub" or "how to make it look pretty?" For the latter, check out https://docs.github.com/en/get-started/writing-on-github. Source: over 3 years ago

Tracking Textile since Mar 2021.