Mkdocs "can not display mermaid in the right way" - mkdocs

I try to use this theme plugin to display the graph
Link:
https://squidfunk.github.io/mkdocs-material/reference/diagrams/?h=mermaid
the settings file:
- pymdownx.superfences:
custom_fences:
- name: mermaid
class: mermaid-experimental
format: !!python/name:pymdownx.superfences.fence_code_format
extra_javascript:
- https://unpkg.com/mermaid#8.6.4/dist/mermaid.min.js
all i got is this..
enter image description here
i dont think it is version problem
Has anyone got any suggestions?thanks

This was part of the insiders offer at your time. If you upgrade your mkdocs-material version it should work.
https://squidfunk.github.io/mkdocs-material/insiders/

Related

What do I add to requirements.txt for font awesome (font-awesome)

SO yeah I'm pretty new to this I used font-awesome for some icons (free version) but after i tried to deploy it to heroku it got some errors, I highly suspect that it is due to requirements.txt, can anyone tell me what I should write in there? I tried font-awesome-free==16.0 but that didnt really work...
Kind of this requirements.txt. You can create
Flask==0.8
Jinja2==2.6
Werkzeug==0.8.3
certifi==0.0.8
chardet==1.0.1
distribute==0.6.24
gunicorn==0.14.2
requests==0.11.1
So that it could fetch or default will work. This is an example

Trying to implement Jekyll via the Poole/lanyon but formatting is not appearing

I'm currently working through my first implementation of a Jekyll webpage (via Github-pages) and I'm trying to use the Poole: Lanyon structure. However, while it seems that the static site is active, it is not picking up any of the formatting.
I can't tell if I needed to add anything else from lanyon github page (https://github.com/poole/lanyon) or if it could have something to do with my '_config' file, which currently looks as follows (or is an entirely different issue):
title: Michael
tagline: 'hopefully a blog2'
description: 'A reserved Jekyll theme that places the utmost gravity on content with a hidden drawer. Made by #mdo.'
url: "/michaelmarzec.github.io"
baseurl: "https://michaelmarzec.github.io"
paginate: 5
permalink: pretty
# About/contact
author:
name: Mark Otto
url: https://twitter.com/mdo
email: markdotto#gmail.com
# Gems
plugins:
- jekyll-paginate
# Custom vars
version: 1.1.0
google_analytics_id: #UA-XXXX-Y
My github repository is here: https://github.com/michaelmarzec/michaelmarzec.github.io
And the attempted website here: https://michaelmarzec.github.io/
Any recommendations or advice will be greatly appreciated!
Looks like I was overthinking this issue - the following was my simple solution:
url: https://michaelmarzec.github.io/
baseurl: ''

Google model-viewer - how to set max zoom?

I'm very happy about what I'm able to do using Google model-viewer. It's relatively configurable, but there's more I'd like to be able to do with the camera-- for instance, setting a max zoom/min distance from the target. I've found code that seems to suggest how to modify this, but I don't know how to override the script delivered via the CDN. Is my only option to download using npm?
Excuse my naivete!
You can see this issue Zoom in/out #1172
Now it's possible to use camera control settings:
max-camera-orbit
min-camera-orbit
max-field-of-view
min-field-of-view
model-viewer(
src="https://cwervo.com/assets/3D-models/logo.glb" ios-
src="https://cwervo.com/assets/3D-models/logo-3m-scaled.usdz"
auto-rotate
camera-controls
min-camera-orbit='auto auto 100%'
max-camera-orbit='auto auto 100%'
min-field-of-view='110deg'
max-field-of-view='110deg'
)
Source: https://codepen.io/schmidtsonian/pen/VwvEwVw
I'm the maintainer of the <model-viewer> project. You aren't crazy; we haven't added the ability to control this yet.
But don't worry! We are planning to add this feature to a release very soon (currently planned for v0.7.0). Please track https://github.com/GoogleWebComponents/model-viewer/issues/458 for progress!
[edit] Also to answer your question about NPM: you can download the module from NPM and assemble a customized version of the pieces that make up <model-viewer>. Also, you could fork the project and patch it that way. I don't necessarily recommend these things, but they are options if you are desperate. If you go this route, I highly recommend asking questions on our Github project page. We are friendly and responsive to everyone.

"Template:!" output from imported MediaWiki template (Infobox)

I am quite new to Mediawiki and am trying to get infoboxes work.
I managed to get a simple one working but am now trying to get the 'Infobox video game' one working.
I am getting the following errors:
Template:!- style="" Template:! Developer(s) || Peter Harrap, Shaun Hollingworth Template:!- style="background: #F0F0F0;" Template:! Publisher(s) || Gremlin Graphics
The page is www.retroresource.co.uk/mediawiki
To try and solve this myself I have been to http://en.wikipedia.org/wiki/Special:Export
and entered in:
Template:Infobox
and
Template:Infobox video game
into the box, ticked all boxes, done a find a replace on replace text/plain with CONTENT_FORMAT_TEXT
I have imported the file through special imports.
I have also copied in the default CSS MediaWiki:Common.css into my own wiki.
What am I missing?
Thanks
You are missing Template:!. MediaWiki 1.24 removed the need for that template, but you are still on version 1.23
You can either update your wiki to 1.24 or add this in Template:!:
<onlyinclude>|</onlyinclude>

For MediaWiki Skin Setting HTML Title to "[Site Name]" instead of "Main Page - [Site Name]"

I'm using a custom version of the monobook skin. How do I set the HTML title to "[Site Name]" instead of "Main Page - [Site Name]"?
You should be able to put something like the following in your common.js, and get it to execute on only the Main Page.
if {{{{PAGENAME}}=="Main Page"
{
document.title = "{{SITENAME}}";
}
It's not totally correct because I don't know javascript.
Try editing [[MediaWiki:Pagetitle]] - set it to "{{SITENAME}}" instead of the default "$1 - {{SITENAME}}".
Perhaps you can use MediaWikis parser functions to achieve something like what Adrian Archer answered, but run by the server rather than the client (so search engines will take heed). You'll have to edit [[MediaWiki:Pagetitle]] as Joshua C. Lerner said, then. Extension:ParserFunctions is bundled with MediaWiki 1.18 and above, so http://www.mediawiki.org/wiki/Help:Extension:ParserFunctions will help you!