A roadmap to learn robotics

[Edward Katz]

As seen on linkedin:

This is a curated GitHub repo for anyone who wants to learn robotics:

A roadmap for learning robotics

[Pito Salas]

I looked at it… Not so sure how curated it is. Looks like the kitchen sink to me…

Best,

Pito

Boston Robot Hackers &&
Comp. Sci Faculty, Brandeis University (Emeritus)

> --
> You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAFMPTVQK2%2B%2BDNpecdo%3DytV%2BFBWU8TNhJD%2BCPW0Wnfzdhe%3DSY9w%40mail.gmail.com.

[Chris Albertson]

My opinion is that it is a good list of online things to investigate. I’ve watched a couple of these tutorials,

But when reading the various email forums and seeing why people have problems, it is almost always that they are lacking in the pre-requests. For example, the project requires Linux and the builder has no clue about Linux, he is reduced to copy/paste “magic gibberish” into the command line and then of course it does not work and the problem is not knowing what “current directory: is, understanding permissions of whatever. Or, maybe you are building an arm or neural network and forget what you used to know about linear algebra (that was me.).

A “roadmap” would be a sequence of steps to be done in order. It would have multiple places on the map where you might start and a few different destinations and the map would tell you how to get from where you are to where you want to be.

There also seems to be a huge divide. In the professional world, “robot” is something that can manipulate objects but in the hobby world is is 99.9% of the “robot" something that rolls on the floor. You find that the professional level education is focused on object manipulation and planning, maybe not what the hobbyist wants.

That said the list is a good start. The next step is to add a short paragraph describing each link. Then add prerequisites and

What this group needs is a Wiki. Then lists like this have a place to live and a lifetime of more than a few days

> To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/A770078C-54F9-4ACE-A3D3-56B26D021E05%40gmail.com.

[Ken Gregson]

"What this group needs is a Wiki. Then lists like this have a place to live and a lifetime of more than a few days" 💯 

And will also benefit from curation to avoid becoming YADF (yet another dumpster fire ;-)

Would a wiki maybe also be a good place to collect group project pages (or is there a better solution for that)?

-Ken

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/A68985EB-50C4-4130-9B34-970EEC0E912C%40gmail.com.

[Stephen Williams]

What I proposed, but haven't had time to get completely working (although I am close), is a static site generator.  I chose Eleventy (aka 11ty) which is popular, one of the better options in that category.  (I have a blank site set up, and I have a remix of the CSS + boiler plate of our current web site: I need to combine those two.

One idea is to have a main web site plus another separate site, ideally using the same mechanism.

A static site generator like this is somewhat close to a wiki, except that creating new pages is creating a text file, usually markdown but could be html or various template alternatives, then triggering (probably automatically) a 'build' that produces the resulting HTML+CSS web site.  The advantage of this over a traditional wiki is that the latter requires a database (or files) drive web app that is generating the actual pages on the fly.  This is slower and less scalable, but does have some nice aspects.  I'm not against having a traditional wiki, but static site generator based websites are nice for several reasons.

The work flow is generally to just add a single text file in articles/my-article.md or myblog/20260429-How-I-Fixed-It.md or similar.  With github + 11ty, we would have a git hook to auto-build the site.

Looking more closely for the crossover of SSGs vs wikis, I find this:

https://github.com/wikibonsai/wikibonsai

This is an example wiki-like site using that:

https://github.com/wikibonsai/garden-beds

This is an example page:

https://github.com/wikibonsai/garden-beds/blob/main/agent/foundation/entries/causality.md

With an image:
https://github.com/wikibonsai/garden-beds/blob/main/minima/bonsai/entries/bonsai.md

It does work with 11ty, and in a number of other configurations.  Mainly, this adds wiki syntax for linking to pages: [[topic name]].

There have been ways to allow direct web editing of files in git.  Something like that might work here, which would make for a much more complete Wiki experience.

There are some other interesting options that work in a similar way:

This says that it converts md to wiki pages, but also has edit.

https://ikiwiki.info/

https://github.com/Linbreux/wikmd

Stephen

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAArUYGtHdD8oO-0nQBS27OhYz0yG5YnFcEN71JHOGcNNf6y48A%40mail.gmail.com.

[Albert Margolis]

The club has had several wiki over the decades of its history. None has ever received updates after a few months. Creating a wiki structure is relatively easy. To make it useful, somebody has to do a lot of work to drive content creation, handle moderation, etc. Unless somebody is committed to do that boring organizational work consistently for an extended period of time, I personally don't think it is worth discussing.

Anybody who wants to do the work should feel to get one started and we can point to it from the main website. We can also point wiki.hbrobotics.org to it.

Just do it!

- Al Margolis

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/589dd366-af3d-44ad-88db-1e077ceac862%40lig.net.

[James H Phelan]

I wonder if one of the AIs could scrape our mailing list and condense it into an organized, summarized trove of HBRC wisdom?  

James H Phelan
"Nihil est sine ratione cur potius sit quam non sit"
Leibniz

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAPFBGAczQkn15usojBh%3D4oTk-%2BYAZq_3fdwwxfUrTmu3zMJ5KA%40mail.gmail.com.

[Chris Albertson]

Whether a wiki or static file generator.    The idea is that anyone can post things like their projects.   They just add it to the Wiki.   

I think the way to decide which software to use is to find the least computer-literate person you know to try and use the candidate software.  Whatever it turns out he can figure out, use that.   It has to be easy enough that anyone can add pages with no knowledge of “web stuff”.   If it takes even 20 minutes of study, it will not be used.

Here is a popular open-source wiki that does not use a database. https://www.dokuwiki.org/dokuwiki

But the reason for using a DBMS is for atomic operations.   DBMSes are good at locking.

On Apr 29, 2026, at 5:37 PM, 'Stephen Williams' via HomeBrew Robotics Club <hbrob...@googlegroups.com> wrote:

What I proposed, but haven't had time to get completely working (although I am close), is a static site generator.  I chose Eleventy (aka 11ty) which is popular, one of the better options in that category.  (I have a blank site set up, and I have a remix of the CSS + boiler plate of our current web site: I need to combine those two.

One idea is to have a main web site plus another separate site, ideally using the same mechanism...

[Ken Gregson]

Oh, I was just assuming something like straight up GitHub markdown wiki pages, perhaps on the existing BRH site. I'm game for anything, especially something easy/new/fun.

Agree with "It has to be easy enough that anyone can add pages with no knowledge of 'web stuff'", WordPress is popular for a reason.

Have used Hugo, Jekyll, and Ghost (plus some older Wiki tools like Instiki and Media/DokuWiki) 11ty is new to me. MkDocs could also be interesting. 

Something low maintenance, easy to add/update, and no hosting fees (or admin'ing) would be attractive. 

It's a little off topic but I've recently been playing with Basecamp (free/personal license) and their open sourced kanban (Fizzy), and chat tools (Campfire). Like them but they would be costly to use for our group(s).

--
You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/0B4248AC-630F-4153-8BF6-4793ECCB2CDB%40gmail.com.

[Wayne Gramlich]

All:

I'm a big fan of GitHub markdown wiki pages.  Almost everybody has to learn
git at some point in time and markdown is trivial to learn.  It supports
parallel content addition/modification/deletion.

HBRC does have a github website: (https://github.com/hbrobotics).  It hasn't
been used for years.

Ultimately, it is up to the club members to decide.

Regards,

-Wayne

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAArUYGsT9nMo6p6%2BBZPvAJKc4cmPfgXtkVsc3jRX%3DgWtgv0VBg%40mail.gmail.com.

[Thomas Messerschmidt]

But whatever happened to markUP languages???? :) 

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/e1320172-6b5b-45e1-9380-09bf1bbfe60d%40gmail.com.

[Albert Margolis]

Markdown has become the most popular markup format for applications where normal humans have to type and review text, especially when they are in a hurry. I think it started in the blogging world and eventually spread to newsrooms. It is plain text that uses syntax that is easy to type correctly and doesn't go off the rails when you make a mistake. Basic formatting features are very simple but the format is very customizable and extensible where needed. The first use was for applications where it was translated to HTML for the web but there are now tools to translate to and from almost any final document format that you want.

It has also become the most popular format for AI. All the LLMs that I use prefer markdown as their communication format. AI skills and memories are most commonly markdown. Agentic system control files are usually markdown. When you upload other text formats, most of the system convert to markdown and then process that.

https://www.markdownguide.org/getting-started/

- Al Margolis

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CADyjTyZBYmWwUoecJRqjDpSoUbtiMi_z4yusv2OKf7qOcs6Apg%40mail.gmail.com.

[Wayne Gramlich]

All:

For a brief history of Markdown please read the
[Markdown Wikipedia Article](https://en.wikipedia.org/wiki/Markdown).
If you folks decide to go down the markdown on GitHub route, I would recommend
standardizing on GittHub Flavored Markdown](https://github.github.com/gfm/).

There are tons of great information being posted to mail list, particularly
through the various SIG's.  It might be fun to pick one SIG and see if you
can figure out how to get a rotation of people cut and paste one week's of
SIG traffic.  Effort is required, but if is spread out over the SIG, it might
be manageable.

Note, I am **NOT** volunteering for any of this effort.  I am *retired*.

Regards,

-Wayne

P.S. My HBRobotics archive goes back to 9Mar2010.

[Chris Albertson]

I think GitHub is for hosting a Wiki related to the project you put on GitHub.   So if the club had a collaborative robot project, you would use the GitHub wiki for documentation.  The “friction” of learn ing curve is “nothing” is you are a software developer using Wiki to host your code.  But for the general user it might seem complex

But I think we are talking about a more general wiki, not tied to a project.   It's kind of an abuse of GitHub to do that.

I did the Google search and found two free Wiki sites that are set up for groups like small clubs and such

(1) Uses “media Wiki” which is the same software as Wikipedia.  We all know what that looks like.   It looks very good https://miraheze.org/

(2) THis one might be easier to use for some people, but the free version has a 200MB size limit. https://slimwiki.com/.      With a 200MB limit, we don’t post videos, only links to YouTube but for text and small photos, 200MB is huge.      The paid version is $48 per year and up to 1GB.   The free version is branded.

Me?  I don’t mind MediaWiki software and would go with them.  But many people think it is over-complex for a small site.   About the two sites #1 has no ads.  It is funded with donations and volunteer workers.  #2 is clearly a for-profit outfit that uses the business model of free for personal use, pay for corporate use.     I’d have to do a small experiment with each.   I think it has to be really easy to use or it will not collect much content.   

On Apr 29, 2026, at 8:20 PM, Stephen Williams <s...@lig.net> wrote:

On 4/29/26 7:37 PM, Chris Albertson wrote:

Whether a wiki or static file generator.    The idea is that anyone can post things like their projects.   They just add it to the Wiki.   

Authoring content as Markdown files is generally accepted as best for everyone for this kind of thing.

I think the way to decide which software to use is to find the least computer-literate person you know to try and use the candidate software.  Whatever it turns out he can figure out, use that.   It has to be easy enough that anyone can add pages with no knowledge of “web stuff”.   If it takes even 20 minutes of study, it will not be used.

The biggest decision is to decide if we are OK being github based or not.  There are situations where even github is too much friction, headache.  Most of us have been assuming at least is fine for us.  Google Drive, s3fs mounts of an S3 service are some other possibilities.

Here is a popular open-source wiki that does not use a database. https://www.dokuwiki.org/dokuwiki

But the reason for using a DBMS is for atomic operations.   DBMSes are good at locking.

Git provides the equivalent of that function.  Also, when adding new content as new files, not typically an issue.

The other solution that avoids locking issues is live editing, like Google Docs.

Stephen

On Apr 29, 2026, at 5:37 PM, 'Stephen Williams' via HomeBrew Robotics Club <hbrob...@googlegroups.com> wrote:

What I proposed, but haven't had time to get completely working (although I am close), is a static site generator.  I chose Eleventy (aka 11ty) which is popular, one of the better options in that category.  (I have a blank site set up, and I have a remix of the CSS + boiler plate of our current web site: I need to combine those two.

One idea is to have a main web site plus another separate site, ideally using the same mechanism...

--
You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/0B4248AC-630F-4153-8BF6-4793ECCB2CDB%40gmail.com.

[Pito Salas]

I 100% agree with this and it was my thought baloon as I saw discussions about various wikis and markdown and so on. That IMHO is the easy part.

The hard (or impossible) part is to actually have someone(s) who is curating, adding and deleting. Just google "ros2 awesome list" and you will see lots of laundry lists of resources which are perhaps up to date and perhaps useful.

Best,

Pito

Boston Robot Hackers &&
Comp. Sci Faculty, Brandeis University (Emeritus)

> On Apr 29, 2026, at 9:46 PM, Albert Margolis <almar...@gmail.com> wrote:
>
> The club has had several wiki over the decades of its history. None has ever received updates after a few months. Creating a wiki structure is relatively easy. To make it useful, somebody has to do a lot of work to drive content creation, handle moderation, etc. Unless somebody is committed to do that boring organizational work consistently for an extended period of time, I personally don't think it is worth discussing.
>

> Anybody who wants to do the work should feel to get one started and we can point to it from the main website. We can also point wiki.hbrobotics.org [wiki.hbrobotics.org] to it.

>
> Just do it!
>
> - Al Margolis
>
>
> On Wed, Apr 29, 2026 at 5:37 PM 'Stephen Williams' via HomeBrew Robotics Club <hbrob...@googlegroups.com> wrote:
> What I proposed, but haven't had time to get completely working (although I am close), is a static site generator. I chose Eleventy (aka 11ty) which is popular, one of the better options in that category. (I have a blank site set up, and I have a remix of the CSS + boiler plate of our current web site: I need to combine those two.
> One idea is to have a main web site plus another separate site, ideally using the same mechanism.
> A static site generator like this is somewhat close to a wiki, except that creating new pages is creating a text file, usually markdown but could be html or various template alternatives, then triggering (probably automatically) a 'build' that produces the resulting HTML+CSS web site. The advantage of this over a traditional wiki is that the latter requires a database (or files) drive web app that is generating the actual pages on the fly. This is slower and less scalable, but does have some nice aspects. I'm not against having a traditional wiki, but static site generator based websites are nice for several reasons.
> The work flow is generally to just add a single text file in articles/my-article.md or myblog/20260429-How-I-Fixed-It.md or similar. With github + 11ty, we would have a git hook to auto-build the site.
> Looking more closely for the crossover of SSGs vs wikis, I find this:

> https://github.com/wikibonsai/wikibonsai [github.com]

> This is an example wiki-like site using that:

> https://github.com/wikibonsai/garden-beds [github.com]

> This is an example page:

> https://github.com/wikibonsai/garden-beds/blob/main/agent/foundation/entries/causality.md [github.com]
> With an image:
> https://github.com/wikibonsai/garden-beds/blob/main/minima/bonsai/entries/bonsai.md [github.com]

> It does work with 11ty, and in a number of other configurations. Mainly, this adds wiki syntax for linking to pages: [[topic name]].
> There have been ways to allow direct web editing of files in git. Something like that might work here, which would make for a much more complete Wiki experience.
>
> There are some other interesting options that work in a similar way:
> This says that it converts md to wiki pages, but also has edit.

> https://ikiwiki.info/ [ikiwiki.info]
> https://github.com/Linbreux/wikmd [github.com]

>> >> To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAFMPTVQK2%2B%2BDNpecdo%3DytV%2BFBWU8TNhJD%2BCPW0Wnfzdhe%3DSY9w%40mail.gmail.com [groups.google.com].

>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
>> > To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

>> > To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/A770078C-54F9-4ACE-A3D3-56B26D021E05%40gmail.com [groups.google.com].

>>
>> --
>> You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

>> To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/A68985EB-50C4-4130-9B34-970EEC0E912C%40gmail.com [groups.google.com].

>> --
>> You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

>> To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAArUYGtHdD8oO-0nQBS27OhYz0yG5YnFcEN71JHOGcNNf6y48A%40mail.gmail.com [groups.google.com].

>
> --
> You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/589dd366-af3d-44ad-88db-1e077ceac862%40lig.net [groups.google.com].

>
> --
> You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAPFBGAczQkn15usojBh%3D4oTk-%2BYAZq_3fdwwxfUrTmu3zMJ5KA%40mail.gmail.com [groups.google.com].

[Thomas Messerschmidt]

Thanks Al. 

I bumped into md a few months back, I was saving a text file In which I had bolded some words thinking that it was great that notepad had been updated. When I tried to save it, notepad told me it wanted to save it as a .md, so I did. I then opened it with notepad++ and got to see all the "pretty" md code. 

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CAPFBGAcGWz68xn1%2BCVzqLvV0Qw6HaJ1FYrhFeSvAydMRfZa9Tg%40mail.gmail.com.

[Stephen Williams]

Miraheze.org is not working for Firefox.

A lot of people like the use of github as it provides all of the control, merging, multi-user, approval that software has.  Content management systems often have various features to try to achieve the same thing.  Wikis are part of this.

If we decide we want a non-git solution, there still is another option that maps to SSGs well: People could set up sshfs or s3fs mounts to the VM / container where the SSG runs to convert inputs to the web site.  Filesystems don't provide versioning by themselves.  S3 object stores generally have a versioning mode that can be turned on.  This solves the editing history of a file. But trying to get a point-in-time snapshot of which version of which files existed would take some kind of tool on top.

Sshfs+FUSE on Linux or SSHFS-Win+WinFsp on Windows works very well and is easy to set up.

S3fs mounts work with a MinIO S3 server or to AWS S3 or a variety of other providers.  Then they can just edit local files which can directly, or more probably indirectly, get promoted to the resulting site.  We can have individual or shared directories.  This is what I often do, and will for some SSG publishing.

S3fs (i.e. s3fs-fuse) works very well, except for one case that we won't have: Do not list a bucket prefix that has millions of objects in it.  In Linux / MacOS, mounting an s3 bucket as a local filesystem is just a simple mount command w/ credentials.  For Windows, there is WinFSP to do what FUSE does, then there are a number of free & paid s3fs mount apps that do what s3fs does.  This would be very convenient for copying in a set of images, videos, etc.

Over the last couple years, I have done a lot with MinIO and NetApp StorageGRID S3 servers, along with AWS S3.

We could even automatically commit the resulting changes to github to get history, and the ability to reset to earlier versions.

Github should be fine for most things we do with git, but git-remote-s3 is interesting: It stores git repos in an s3 object store.  This can be convenient when everything else is stored in S3 too.

Looking again at Wiki-like SSG approaches, I find these:

https://www.mkdocs.org

https://docusaurus.io

https://mcshelby.github.io/hugo-theme-relearn

https://silverbullet.md

https://quartz.jzhao.xyz

That said, there are many nice wikis.  We would likely want to run one on our own system / VM / container somewhere.  That should be least expensive with the least restrictions on space.  But these tend to have more lock-in than SSGs using markdown files.

Stephen

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/C7E22F61-5348-465F-AF08-91A4792EA0FB%40gmail.com.

--

Stephen D. Williams Founder: VolksDroid, Blue Scholar Foundation 650-450-8649 | fax:703-995-0407 | s...@lg.net | https://VolksDroid.org | https://BlueScholar.org | https://sdw.st/in

[Steve " 'dillo" Okay]

On Thursday, April 30, 2026 at 5:39:01 AM UTC-7 Albert Margolis wrote:

Markdown has become the most popular markup format for applications where normal humans have to type and review text, especially when they are in a hurry. I think it started in the blogging world and eventually spread to newsrooms. It is plain text that uses syntax that is easy to type correctly and doesn't go off the rails when you make a mistake. Basic formatting features are very simple but the format is very customizable and extensible where needed. The first use was for applications where it was translated to HTML for the web but there are now tools to translate to and from almost any final document format that you want.

It has also become the most popular format for AI. All the LLMs that I use prefer markdown as their communication format. AI skills and memories are most commonly markdown. Agentic system control files are usually markdown. When you upload other text formats, most of the system convert to markdown and then process that.

It also benefits from having a number of reasonably lightweight FOSS editors available on Linux, does not feature-chase or require new font packs. You don't have to worry if a .MD written on Windows will open in Linux or reserve your next lifetime for mastering a whole documentation system like with HTML & CSS. 

I use Typora and it has been great for loading in README.mds, editing them and having them show up on my Github project's page exactly like it did in the editor. 

I submitted a proposal for ROSCON last week in Markdown and wrote up a whole documentation set for a client project with OpenNav last year using it.  

'dillo

[Chris Albertson]

OK, I looked.  https://github.com/hbrobotics/hbrc_robots/wiki

As of right now (May 1, 1:37 pm) the page the page looks like this

Welcome to the hbrc_robots wiki!

Wikis provide a place in your repository to lay out the roadmap of your project, show the current status, and document software better, together.

It seems that anyone can edit it and while the text is saved on Markdown, there is a WYSIWYG editor.     I just chan ged ikt to a page asking for someone to plaes roll back the changes I just made.

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/CADyjTyYkg0fiqT8bTiS9mUR%3DpJhOgHK-n7T9CuVEDOc%3DgnikKg%40mail.gmail.com.

[Wayne Gramlich]

All:

I had nod idea that HBRC Github based wiki available.
I 99% sure somebody other than me set up the entire HBRC GitHub.

Regards,

-Wayne

[Ken Gregson]

Why roll-back when you can run forward?

I guess this could work? Seems easy to add/edit/update. Curation will be the deal make/breaker. Even though the link I just added on the "new" 'ROS 2 Learning Roadmap' Page is to the not even yet officially released ROS 2 Lyrical tutorial docs, that will age quickly ;-)

https://github.com/hbrobotics/hbrc_robots/wiki

BTW, if you've ever wanted a no pressure on-ramp to support the entire ROS community, joining the Lyrical Test and Tutorial Party could be that opportunity!

https://discourse.openrobotics.org/t/lyrical-luth-test-and-tutorial-party-instructions/54427

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/c223360f-f771-48d2-bbce-4807d694fa19%40gmail.com.

[Chris Albertson]

Why roll back? I just wondered how to do that or if it was even possible. Making changes was easy, but can you revert them without recreating the old state? I assume it must be possible, but I wasn't able to figure it out in 30 seconds.

The biggest problem, obviously, is that no one uses this wiki or even knows it exists. I'm not 100% sure that a wiki buried in GitHub will get noticed. Unless we do something like put a link to the wiki in every email. But there is already four lines of text that no one reads—why add a fifth?

Typically, to get these things started, someone has to make an effort to upload useful content and include links leading to yet-to-be-written pages with a note saying “please write something here." The content has to be good enough that people remember to check the wiki, and once search engines take notice, it can gain momentum.

The #1 rule for getting your site noticed is not advertising but providing content that is in demand.

[camp .]

Yahoo Mail: Search, Organize, Conquer

--

You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/hbrobotics/BD61262E-C9BB-4ECB-B85F-51CD1E9546D1%40gmail.com.