Git Product home page Git Product logo

Comments (2)

twostraws avatar twostraws commented on September 15, 2024

I'm sorry you feel the current documentation is incomplete, but I have very little interest in pursuing DocC for Ignite documentation.

I spent a great deal of time building https://ignitesamples.hackingwithswift.com, which a) shows off almost every element type and modifier, b) provides the code used to create each sample, and c) is written entirely in Ignite; I'd much rather improve that if something is missing.

The benefit of having it built in Ignite is that folks can literally take our sample code as-is and use it however they want – it's neatly recursive, and also acts as a demo site for folks who want to see what Ignite can do.

from ignite.

Jeehut avatar Jeehut commented on September 15, 2024

Fair enough, I do understand the point to use Ignite for its own documentation. But then I have a couple of suggestions:

  1. Instead of calling the site 'Ignite Examples' I suggest making it the official 'Ignite Documentation'
  2. The Getting Started guide from the README should live there as well in a 'Guides' section
  3. Instead of 'Examples' there should be sections with all components listed, easy to look up things
  4. For dedicated articles explaining multiple components that belong together, the 'Guides' section could be used
  5. An 'Examples' section could be reintroduced for entire real-world use cases like an app landing page, a blog, etc.

Due to these points above, the examples site doesn't feel like documentation to me. For example, I was looking for a way to add metadata to my pages for SEO purposes, but I couldn't find the MetaTag component there. So I looked for the word "documentation" on the Ignite repo and couldn't find anything that lead to more info. It should be listed somewhere though and a dedicated guide on topics like "SEO", "Deployment", or "File structure" could be very useful as well.

Much like Vapor has guides on different topics, including dedicated instructions for common deployment providers. I found their guided & structured documentation very helpful in piecemeal adoption of a new technology I've never used before.

Creating websites is a complex topic with many aspects to consider and learn about. A README and a website with an incomplete list of alphabetically ordered component explanations doesn't seem to make it justice. At least there are some things missing, even if you don't agree with my renaming suggestions.

I hope I could help clarify why I created this issue in the first place. If you closed it only because you disagree with my DocC suggestion, I would appreciate if you opened it again until the incomplete docs are fixed. I removed DocC from the title.

from ignite.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.