Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 20:59
    squidfunk commented #2772
  • 20:58
    squidfunk commented #2772
  • 20:57
    squidfunk closed #2772
  • 20:57
    squidfunk commented #2772
  • 20:44
    Stanzilla commented #2772
  • 15:15
    Stanzilla commented #2771
  • 05:40
    squidfunk commented #2771
  • 05:38
    squidfunk commented #2772
  • 00:30
    Stanzilla opened #2772
  • 00:27
    Stanzilla edited #2771
  • 00:27
    Stanzilla edited #2771
  • 00:27
    Stanzilla edited #2771
  • 00:27
    Stanzilla edited #2771
  • 00:27
    Stanzilla opened #2771
  • Jun 18 18:52
    Mopster closed #2770
  • Jun 18 18:52
    Mopster commented #2770
  • Jun 18 18:48
    Mopster edited #2770
  • Jun 18 18:43
    Mopster opened #2770
  • Jun 17 09:39

    github-actions[bot] on gh-pages

    Deployed a4a00af with MkDocs ve… (compare)

  • Jun 17 09:38
    squidfunk labeled #2761
Martin Donath
@squidfunk
That would mean multiple builds that need to be merged.
Radim Vančo
@FoxKyong
Hi. Is there somewhere still the old version of documentation which had examples of everything on one page? I didn't use it for a while and I can't find it anymore. I think the documentation was changed during the end of the year and I can't find in the new one these examples and some things at all. It was much better for understanding how to write specific examples and I need it for other people who don't know markdown at all and they need page with those examples, the current reference page is too difficult for them.
Martin Donath
@squidfunk
@FoxKyong do you mean the specimen page?
The documentation was restructured in the middle of last year. The reference now contains all previous (and more) examples: https://squidfunk.github.io/mkdocs-material/reference/abbreviations/
Radim Vančo
@FoxKyong
I think so. I am not sure how it was called before but for quick reference it was better at least for some people. It was pretty quick to just scroll there and find an example of what exactly what you want to do. I had it cloned but only for a limited time. The new reference is good detailed in some ways but for just quick examples for people who don't know markdown it is much harder.
Martin Donath
@squidfunk
Just check out any of the 5.x releases, I think we had it there.
After all thats what git is for 😉
Radim Vančo
@FoxKyong
Ok, thanks. I can't find it in the latest 5.x now, I'll check other versions later.
Martin Donath
@squidfunk
Maybe 4.x, I can't remember exactly when we removed it.
Or search for specimen.md in the git history, that was the name of the file.
oprypin
@oprypin:matrix.org
[m]
@squidfunk: facelessuser
https://gitter.im/squidfunk/mkdocs-material?at=60b88a770ff6de262b441e6c
https://gitter.im/squidfunk/mkdocs-material?at=60bcfca419b46c60b170f300
^
Seeing these messages made me more confident in suggesting that I become the maintainer of MkDocs:
https://github.com/mkdocs/mkdocs/discussions/2442
But instead, the idea of a separate "issue-closing committee" took over, which I don't know if it's actually happening or what it will solve. What I see is that things seem to be fizzling out.
I'm ready to push things forward if given the opportunity. If you mean to express your support, please do so in that thread; it looks like I will need that.
Martin Donath
@squidfunk
I just wanted to help out in reducing the number of open issues
facelessuser
@facelessuser:matrix.org
[m]
The current discussion seems to be about reducing open issues and gaining an understanding of what people feel is missing.
Martin Donath
@squidfunk
Honestly, it's very hard to catch Tom, so my aim with this was to lend my frontend knowledge to decide on frontend related issues whether they can be closed as out of scope or not. There're many issues with "needs design decision" and I thought I could maybe help provide some input to reach a decision.
oprypin
@oprypin:matrix.org
[m]
right-- you can see those things as separate and not conflicting. sorry if I'm misconstruing that
Martin Donath
@squidfunk
Tom already suggested that we make this an open call, I'm also open to that.
facelessuser
@facelessuser:matrix.org
[m]
Yeah, I think Tom is just feeling out right now to get a better understanding of what MkDocs "needs". He's been quite removed for some time.
Martin Donath
@squidfunk
Regarding maintainership: yes, it would be great to see progress. I think Tom is currently thinking of moving MkDocs under the Encode organization which should make the management easier, but hasn't reached a decision yet.
facelessuser
@facelessuser:matrix.org
[m]
I think having someone, or at least a committee that at least steers the vision of a project is still important.
Benjamin Staneck
@Stanzilla
from previous experiences: never give ownership to one person, and never to a group of 3, always even numbers :D
Martin Donath
@squidfunk
I think the question is not whether to transfer ownership, but just grant maintainer rights
oprypin
@oprypin:matrix.org
[m]
well i mean mkdocs has been one person for quite a long time now
and the alternative is 0 person so yeah...
Martin Donath
@squidfunk
I hope we can find a decision soon, because issues and PRs are piling up and with 1.2 out the door I'd expect more stuff to roll in.
oprypin
@oprypin:matrix.org
[m]
not to be a populist or anything, but I am, in fact, offering an easy solution to that
Martin Donath
@squidfunk
I'm not the one to decide, so I can only speak to Tom trying to find a way to move things forward. In the end, it's the authors' decision, and that's Tom and Dougal.
Offering some time for a grooming session was my way of trying to move things forward.
oprypin
@oprypin:matrix.org
[m]
that offer can be valuable in later stages, but alone I don't think it can move things
Martin Donath
@squidfunk
Okay, so you suggest that you become a maintainer first, and then?
oprypin
@oprypin:matrix.org
[m]
well first of all, then contributions can be accepted.
Martin Donath
@squidfunk
I'd question the value of accepting contributions without clearing out and defining the vision beforehand. Bugfixes, yes, but I think MkDocs really needs a sharpening of focus.
oprypin
@oprypin:matrix.org
[m]
issues themselves don't bother me too much (in terms of their number), it's possible to find trends even without closing them. but there are indeed some easy ones to close. when some issues that are unclear are identified, then it's good to discuss
Martin Donath
@squidfunk
Yes, that was the idea of the grooming. Closing what's definitely out of scope or support requests, so the more interesting stuff is allowed to surface.
oprypin
@oprypin:matrix.org
[m]
sharpening of focus always correlates with dedicated leadership, from what i've seen
Martin Donath
@squidfunk
It would be interesting to see what you would imagine for the project, i.e. what your vision is. You seem to be heavily invested, which is great, but the question is whether this aligns with the philosophy of MkDocs. I think if you would take some time and lay out your vision of the project and where you think it should head, a decision might be easier to find. That's just an idea.
Don't get me wrong. I think you could be a great fit, because you manage some larger documentations with dedicated needs, but as the creator of a project, I would want to make sure it keeps on living in a way that I imagined it to do.
That's at least what I would do, if I'd need to.
oprypin
@oprypin:matrix.org
[m]
frankly, I don't think I'm willing to write out a vision document specifically so that people can judge me over it. I don't actually have even a general roadmap right now -- I think that comes with enough time spent observing the trends. which again I'm not willing to invest that much upfront, looking at this general very low level of trust.
oprypin
@oprypin:matrix.org
[m]
alright then, let's wait and see what happens
Martin Donath
@squidfunk
Hehe
Martin Donath
@squidfunk
@oprpyin I'm seeing sporadic errors when using mkdocs serve in 1.2.1 on macOS. The server seems to keep working, although the errors are printed to the console:
Bildschirmfoto 2021-06-17 um 08.48.00.png
Martin Donath
@squidfunk
I'm just asking you because IIRC you implemented the new livereload server, or am I wrong?
oprypin
@oprypin:matrix.org
[m]
squidfunk (Martin Donath): don't know about the first big error. from this article http://erickt.github.io/blog/2014/11/19/adventures-in-debugging-a-potential-osx-kernel-bug/ (Ctrl+F "cleanly") i'd say that this is just the server trying to send data when the browser already closed the connection. most people seem to say that showing this particular error in that situation is a bug in macos. it should be safe to catch and ignore, but maybe there's no opportunity to catch it, as the stack trace doesn't show any place where it's "our" code
@squidfunk: the 404 error comes from a site with an old MkDocs version still running in one of your browser windows. could also be causing the other error.
Martin Donath
@squidfunk
Thanks for investigating. I'll check whether I still have an older MkDocs site running.
lampensau
@lampensau
hey there, quick question: Is there a way to directly link to a specific "content tab" in a document? (https://squidfunk.github.io/mkdocs-material/reference/content-tabs/)
oprypin
@oprypin:matrix.org
[m]
@lampensau: seems not
lampensau
@lampensau
@oprypin:matrix.org thanks for answering!