-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tutorials & description #41
Comments
Would this all be best bundled as part of a website? Not sure what your background in web development is like, but I would recommend going with a Jekyll site and its integration with Github pages. It wouldn't allow for a true anyone-can-edit-this Wiki, but it means we can keep documentation in the repository source and easily bundle updates to the site/resources with releases. If that sounds good I can setup the basic infrastructure and maybe do some light customisation of an off the shelf theme. |
Sounds good to me. Let's use GitHub Pages and Jekyll. |
Great, will add a PR in a sec that has the basic structure. A |
Domain sandworm.la is ours now. Where should I point it to? |
The instructions should be over here. The instructions for enabling the page itself are also located here (enabling it requires full repo access). I guess we could enable it sooner rather than later (along with a 'work in progress note'?) as I don't imagine it will be linked to anywhere. |
Done. Both sandworm.la and www.sandworm.la should be pointing to the docs now |
Looking at the list of officially supported themes, I like this one: |
Ah, this should be fixed in If you prefer the look of the minimal theme I can customise our use of the current theme to bring it closer to that style. I'd be keen to try and add a bit more personality that can match the color schemes in the draft logo. Either way, just the docs is probably a better starting theme as it provides features like search, subpages, and a few other things that are useful to build on. |
@philipbelesky, @BarusXXX, I've put together a promo video for our plugin: The idea is to share it with the wider community, now that it is officially available. A few questions:
Any other ideas? |
Great work! A very fun beat and showcase
All good!
That sounds good, I've setup a
|
Great! Where does sandworm.la pull the data from? Should we just edit the readme file and it will get mirrored on the website? |
The data is in markdown files under Each markdown file has a header with some template specific information so the README can't be directly mirrored, but the content can be copied over directly. If you're using the windows linux subsystem it should be pretty easy to get a local installation going. With terminal or powershell it probably needs a Ruby install. I'd be happy to run through the setup if useful! Or, you could write the Markdown directly and we can adjust as we go. |
Thanks, I'll start with writing te Markdown and see how well this goes. |
@philipbelesky, I've just put together a short intro video on how to use SW: Let's update the website now and make it all public soon. |
I tried updating this file but with mixed results. Some changes were picked up by the website immediately, some didn't go through at all. Here is what I see in the editor: Is there a way to force-rebuild the content? |
I presume the changes in If having per-branch previews of the website was useful, I could setup the site to run on Cloudflare Pages rather than Github (I would need full repo access though). |
Oh, also, that's a great tutorial video! |
Thanks! There is a slight lag between the commit and the website being rebuild which lead me to believe, that it actually builds from the feature branch. No need to setup per-branch previews of the website. It works well as is. I've updated some basic info on the Now we're also live on Food4Rhino. Let me know if you have any content you want to be added there. |
Great! The footer string is set over here: Line 42 in e5a0bda
|
We need a way to inform future users on what SandWorm can do and how to get there. Some ideas:
The text was updated successfully, but these errors were encountered: