cheng/wallet
0
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
462d436039
wallet/docs/pandoc_templates/mkdocs.cfg

46 lines
1.4 KiB
INI
Raw Normal View History

put in the machinery for a navbar, a navcolumn and a banner. Broke all my existing markdown builds, because I have a hundred files that do not fit the new machinery And now I have to provide navbars for each directory, and update the mkdocs.sh in each directory And add a recursive invocation of mkdocs in subdirectories
2023-08-25 17:45:47 -04:00
if [[ "$OSTYPE" == "linux-gnu"* ]]; then
osoptions=""
elif [[ "$OSTYPE" == "darwin"* ]]; then
osoptions=""
elif [[ "$OSTYPE" == "cygwin" ]]; then
osoptions="--fail-if-warnings --eol=lf "
elif [[ "$OSTYPE" == "msys" ]]; then
osoptions="--fail-if-warnings --eol=lf "
fi
Finally completed amending my html generation from markdown to the new cool style imitating other successful open software movements. But all my navbars are the same navbar. The point of the new style is to make information readily available. We will want multiple button bars in the navbar, and possibly a related materials sidebar. Or perhaps simply link pages. We also need to change the introductory paragraph in every page to the abstract style.
2023-10-26 03:12:35 -04:00
if [[ -z $targetDocroot ]]; then
targetDocroot=$docroot
fi
conforming the mkdocs structure to dry
2023-10-26 20:12:00 -04:00
echo "${PWD##*/}"
Finally completed amending my html generation from markdown to the new cool style imitating other successful open software movements. But all my navbars are the same navbar. The point of the new style is to make information readily available. We will want multiple button bars in the navbar, and possibly a related materials sidebar. Or perhaps simply link pages. We also need to change the introductory paragraph in every page to the abstract style.
2023-10-26 03:12:35 -04:00
options=$osoptions"--toc --number-sections --toc-depth=5 --from markdown+smart+raw_html+fenced_divs+bracketed_spans --to html5 --wrap=preserve --metadata=lang:en --css=$targetDocroot"pandoc_templates/style.css" -Bnavbar -o"
for f in *
put in the machinery for a navbar, a navcolumn and a banner. Broke all my existing markdown builds, because I have a hundred files that do not fit the new machinery And now I have to provide navbars for each directory, and update the mkdocs.sh in each directory And add a recursive invocation of mkdocs in subdirectories
2023-08-25 17:45:47 -04:00
do
Finally completed amending my html generation from markdown to the new cool style imitating other successful open software movements. But all my navbars are the same navbar. The point of the new style is to make information readily available. We will want multiple button bars in the navbar, and possibly a related materials sidebar. Or perhaps simply link pages. We also need to change the introductory paragraph in every page to the abstract style.
2023-10-26 03:12:35 -04:00
if [[ -d $f && -x $f/mkdocs.sh ]]; then
echo "recursing into" $f
$f/mkdocs.sh
conforming the mkdocs structure to dry
2023-10-26 20:12:00 -04:00
dirx=`dirname $0`
dirx="${dirx%/}" # strip trailing slash (if any)
subdirx="${dirx##*/}"
echo "resuming "$subdirx
Finally completed amending my html generation from markdown to the new cool style imitating other successful open software movements. But all my navbars are the same navbar. The point of the new style is to make information readily available. We will want multiple button bars in the navbar, and possibly a related materials sidebar. Or perhaps simply link pages. We also need to change the introductory paragraph in every page to the abstract style.
2023-10-26 03:12:35 -04:00
fi
if [[ $f =~ (.*)".md"$ ]];then
base=${BASH_REMATCH[1]}
if [[ $f -nt $destdir$base.html ]]; then
katex=""
line=""
for i in 1 2 3 4 5
do
read line
put in the machinery for a navbar, a navcolumn and a banner. Broke all my existing markdown builds, because I have a hundred files that do not fit the new machinery And now I have to provide navbars for each directory, and update the mkdocs.sh in each directory And add a recursive invocation of mkdocs in subdirectories
2023-08-25 17:45:47 -04:00
Finally completed amending my html generation from markdown to the new cool style imitating other successful open software movements. But all my navbars are the same navbar. The point of the new style is to make information readily available. We will want multiple button bars in the navbar, and possibly a related materials sidebar. Or perhaps simply link pages. We also need to change the introductory paragraph in every page to the abstract style.
2023-10-26 03:12:35 -04:00
if [[ $line =~ katex ]];then
katex=" --katex="$docroot
fi
done <$f
Fixed my plan for making SWIFT into Bitmessage, added a link to it from socil networking
2024-08-06 04:37:28 -04:00
echo "$destdir$base.html from $f"
Finally completed amending my html generation from markdown to the new cool style imitating other successful open software movements. But all my navbars are the same navbar. The point of the new style is to make information readily available. We will want multiple button bars in the navbar, and possibly a related materials sidebar. Or perhaps simply link pages. We also need to change the introductory paragraph in every page to the abstract style.
2023-10-26 03:12:35 -04:00
pandoc --variable $banner_height --variable targetDocroot:$targetDocroot --template $docroot"pandoc_templates/pandoc.template" $katex $options $destdir$base.html $base.md
#else
# echo " $base.html up to date"
fi
fi
put in the machinery for a navbar, a navcolumn and a banner. Broke all my existing markdown builds, because I have a hundred files that do not fit the new machinery And now I have to provide navbars for each directory, and update the mkdocs.sh in each directory And add a recursive invocation of mkdocs in subdirectories
2023-08-25 17:45:47 -04:00
done
conforming the mkdocs structure to dry
2023-10-26 20:12:00 -04:00
echo done with "${PWD##*/}"
Reference in New Issue Copy Permalink