Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • Sign in / Register
Docs and Developer Site
Docs and Developer Site
  • Project overview
  • Repository
  • Issues 4
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 7
  • CI / CD
  • Security & Compliance
  • Packages
  • Wiki
  • Snippets
  • Members
  • Collapse sidebar
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Minds
  • Docs and Developer SiteDocs and Developer Site
  • Issues
  • #18

Closed
Open
Opened 3 weeks ago by Jim Toth@jim-toth:milky_way:2 of 2 tasks completed2/2 tasks
Report abuse New issue

Add Windows environment notes / guide

I wrote a blog post detailing the necessary steps to get a working Minds development environment under Windows 10. I'd like to get the information included in the official documentation.

Hi, @omadrid, @ottman asked me to tag you for feedback on this as I'm unsure how this information would fit in to the current docs structure as the vast majority of the information in my post is only relevant to Windows developers.

My initial suggestion is to re-write the original blog post using markdown and adding it as a "blog" on the docs site itself. This "blog" feature isn't enabled on the docs app but it might be a good place to put blogs/articles/guides that are more specific than the pages in the existing Guides section. (e.g. I was thinking of writing another post about running the front-end natively as a follow up to my windows environment post) I'm mostly just looking for some feedback of where I should put this information that makes sense so Windows devs would see it without having to go looking. I'll submit a merge request with changes once we decide on how it should go.

  • Re-write blog post with markdown as a docs blog
  • Add windows issues to troubleshooting section in docs
Edited 2 weeks ago by Jim Toth

Related issues
0

Related merge requests
1
  • Windows guide 18
    !21
When this merge request is accepted, this issue will be closed automatically.
  • Discussion 5
  • Designs 0
  • Jim Toth :milky_way: @jim-toth changed the description 3 weeks ago

    changed the description

  • Bill Ottman :dragon_face: @ottman added Bounty T - Community labels 3 weeks ago

    added labels

  • Bill Ottman :dragon_face: @ottman added Platform::Browser Priority::2 - Normal Product::Docs Status::Backlog Type::Feature scoped labels 3 weeks ago

    added scoped labels

    • Bill Ottman
      Bill Ottman :dragon_face: @ottman · 3 weeks ago
      Owner

      Right now https://developers.minds.com/docs/contributing/contributing/#ways-to-contribute directs to https://gitlab.com/groups/minds/-/issues?label_name%5B%5D=Bounty.

      Realistically it should link to a page with an explanation of how bounties work and the gitlab link should be linked from there as a list of open bounties.

      So @jim-toth, if @omadrid agrees, I would move your recommended bounty page/outline under to https://developers.minds.com/docs/contributing/contributing/

    • Collapse replies
    • Jim Toth
      Jim Toth :milky_way: @jim-toth · 3 weeks ago
      Guest

      This issue is for the windows troubleshooting / guide. I made a separate issue for bounty / contribution stuff here: #19

    • Please register or sign in to reply
  • Bill Ottman :dragon_face: @ottman added to epic &50 3 weeks ago

    added to epic &50

  • Jim Toth :milky_way: @jim-toth assigned to @jim-toth 3 weeks ago

    assigned to @jim-toth

  • Olivia Madrid
    Olivia Madrid @omadrid · 3 weeks ago
    Developer

    Hey, cool! Looking forward to your contributions :nerd: Sounds like the best course of action is exactly what you've listed in your checkboxes in the issue description. Transform the content of your Minds blog into markdown, enable docs blogs and add it to the developer site as a blog, and then synthesize a few of the most salient points from the blog and add them to the existing docs (this could end up being in Troubleshooting or Installation... there's already a little bit just for Linux users in Installation so a blurb for Windows users wouldn't be totally out of place. Feel free to re-arrange that bit if it makes sense to do so).

    Seems like you're familiar with the docs already, but just in case, please take 15s to make sure you've read about headers first!

  • Ben Hayward
    Ben Hayward @benhayward.ben · 3 weeks ago
    Developer

    Just ccing @xander-miller as I know he's been playing with the stack on Windows.

  • Jim Toth :milky_way: @jim-toth mentioned in merge request !21 2 weeks ago

    mentioned in merge request !21

  • Jim Toth :milky_way: @jim-toth marked the task Re-write blog post with markdown as a docs blog as completed 2 weeks ago

    marked the task Re-write blog post with markdown as a docs blog as completed

  • Jim Toth :milky_way: @jim-toth marked the task Add windows issues to troubleshooting section in docs as completed 2 weeks ago

    marked the task Add windows issues to troubleshooting section in docs as completed

  • Jim Toth :milky_way: @jim-toth changed title from (feat) Add Windows environment notes / guide to Add Windows environment notes / guide 2 weeks ago

    changed title from Add Windows environment notes / guide to Add Windows environment notes / guide

  • Jim Toth
    Jim Toth :milky_way: @jim-toth · 36 minutes ago
    Guest

    @omadrid I think this is good to go, could you merge it when you get a chance?

Please register or sign in to reply
Assignee
Jim Toth's avatar
Jim Toth @jim-toth
Bounty Program Launch
Epic
Bounty Program Launch
None
Milestone
None
Time tracking
No estimate or time spent
None
Due date
None
7
Labels
Bounty Platform::Browser Priority::2 - Normal Product::Docs Status::Backlog T - Community Type::Feature
None
Weight
None
Confidentiality
Not confidential
Lock issue
Unlocked
5
5 participants
user avatar
Jim Toth
user avatar
Ben Hayward
user avatar
Olivia Madrid
user avatar
Bill Ottman
user avatar
Xander Miller
Reference: minds/docs#18