Giter Site home page Giter Site logo

Comments (6)

zenflow avatar zenflow commented on May 25, 2024 1

Mainly I am just thinking about the content that is in tables, like "Configuration" (params) and "Methods". We could pull in that content and present it however we like.

There is not even a need for those tables to be the same across repos. For example, one repo might have an extra column for "Type" in it's Configuration table. Another repo might not have any table for "Configuration".

That said, we could try modestly to keep them relatively uniform, since it seems to be more pleasing to nerds.

from sweetalert2.github.io.

acupofjose avatar acupofjose commented on May 25, 2024

@zenflow to be clear, this would mean a uniform documentation layout for all the repos correct? Each repo would contain their own documentation/*.md that would be aggregated here?

from sweetalert2.github.io.

zenflow avatar zenflow commented on May 25, 2024

to be clear, this would mean a uniform documentation layout for all the repos correct?

No

Each repo would contain their own documentation/*.md that would be aggregated here?

Yes

No need for the organization to be uniform, and I think keeping that synced across repos could end up being a pain.

from sweetalert2.github.io.

zenflow avatar zenflow commented on May 25, 2024

Since documentation was removed from the core repo in #837, I think this is no longer necessary.

I think it's fine to have the documentation live only in this repo.

from sweetalert2.github.io.

zenflow avatar zenflow commented on May 25, 2024

I reopened this because at this moment it seems like our lives would be a bit easier/more-efficient if we had the documentation content live in the same Git repository as the things it's documenting.

If you look at the issues right now, you'll see that this repo is lagging behind the core repo, and a bunch of issues have piled up for changes that [if we pulled content from core repo] would have been included in their related PR in the core repo.

from sweetalert2.github.io.

limonte avatar limonte commented on May 25, 2024

This is all cool and smart, but having a build process for the documentation of the plugin for popups/toasts seems like overengineering to me.

The current page is just fine, KISS.

most systems work best if they are kept simple rather than made complicated; therefore simplicity should be a key goal in design and unnecessary complexity should be avoided

#20 (comment)

from sweetalert2.github.io.

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.