Closed pwnwriter closed 10 months ago
Also i'm sorry, I should have checked it before
You don't need to provide v0.1.2 or You can proceed with just the version eg:
./releaser.sh 0.1.2 # or soo
Seems like aliesbelik/presenterm is making a pr . i'm letting you guys make changes !
Yes ! I got everything you said , I'll make changes and resolve tomorrow morning! Gotta sleep rn.
Another one: the links in the root README file in the repo point to various places in the docs, e.g. in the "features" section. Those should now point to /docs/src
. Once this is deployed we can make them point to the mdbook but until then they should point somewhere valid.
Another one: the links in the root README file in the repo point to various places in the docs, e.g. in the "features" section. Those should now point to /docs/src. Once this is deployed we can make them point to the mdbook but until then they should point somewhere valid.
I think we can streamline the home README by including only essential information and providing a direct link to the documentation?.
I like having the list of features showing up near the top given there's various tools that serve the same purpose but I think presenterm has more features than the rest of them so that's the big differentiator.
Merging this against an intermediate branch. Will make changes and merge to master once it's ready.
Thanks @pwnwriter !
Hello @mfontanini,
There's so much happening that I'd like to rearrange some things to make the process smoother.
I've included a book that utilizes mdBook with the catppuccin theme alongside the default ones. Mdbook ci will run on every new push on master branch and update your docs automatically to new branch called
book
Deployed here: Presenterm Netlify Deployment
I tried using GitHub Pages, but it wasn't rendering assets.
GitHub Pages deploy: Presenterm GitHub Pages Deployment
So, I suggest sticking with Netlify.
Feel free to remove or add anything; I'm open to whatever changes you think are suitable. :v: