So I have been somewhat hesitant of going with a flat-file approach, and I think that is the disconnect. I think a system that starts based on flat files is a little quicker to get off the ground, maybe, but a little tougher to things like guest authorship and the sort of graduated permissions that that might entail. I also think it makes it a little tougher to construct sophisticated content relationships.... relating a blog articles, to an event, to plugins, to user comments.... all easier if the content comes from a relational DB than if the content comes from flat files.
...but ease of authorship is the most important piece and it seems pretty clear from this thread anyway, that most Jenkins folks would rather submit a text file to a repo then type into a text form. ...so first problems first. You can always index flat files later or add various linky-bit-widgets to templates that help reaggregate content and add things like interactive comments and message threads. ....Slide gets the future bit that I am hoping to push towards, so I appreciate that quite a bit. On Wed, Oct 7, 2015 at 10:14 AM, Kohsuke Kawaguchi <[email protected]> wrote: > Exactly this. I feel like there's a disconnect. To me, it reads like we > are actually mostly in agreement. > > > 2015-10-07 2:25 GMT-07:00 Daniel Beck <[email protected]>: > >> jieryn <[email protected]> wrote: >> >> > Show me the beef. Where's the repo? >> >> Right now, we don't have a Git repo or pull requests, because it's Drupal >> rather than a static site. The site doesn't even integrate with the common >> Jenkins community accounts (or GitHub) that everyone already has. >> >> > Seriously, this idea is so obvious I almost hate to mention it. >> >> >> Tyler, KK, and I all think a generated static site, backed by a public >> GitHub repo, is the way to go. Then we'll have the backend that enables >> people to send PRs for everything (not just new content pages, but >> improvements to the layout etc.). >> >> IOW I think you'll be happy with where we're going if we're going in the >> direction we currently favor :-) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/028BCF07-6D8C-4252-92F1-6AE52CED2C1E%40beckweb.net >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Kohsuke Kawaguchi > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/EMbE3a4u8nA/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4ycOmCXnogaKtL9aGtzd%3DvSW1t42auVoNQsrmEZLRCjtg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4ycOmCXnogaKtL9aGtzd%3DvSW1t42auVoNQsrmEZLRCjtg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAOcHHXwMQ4OPg-RX1RfZkQJ6_doRp0s1y6Yko8o-xAnNV4DQjA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
