Remove and gitignore .info.pod files

[bbb651]

I'm working on a little wiki importer and this tripped it up.

By the way, is it alright to include an imported copy of the wiki with my wiki frontend? It is MIT but I just want to make sure, it's not good to have duplicate information that will get outdated, but unfortunately as the json format is right now I don't think it's possible to make the conversion completely automated due to how generic the label component is, the example would ideally look more like:

---

title

The title displayed in the middle of the window bar.

x

The position of the window on the screen on the x axis.

y

The position of the window on the screen on the y axis.

width

The width of the program surface.

height

The height of the program surface.

---

But the current format has no concept of subheadings, inline code, and soft line breaks seem to be baked in as hard ones, making it pretty much impossible.

I also don't mind moving it to this organization if you're interested (although the name would probably need to be changed to something else because Picotron-Software-Developers.github.io is a bit of a mouthful, I contacting github support to get the picotron name as it has never had any activity in a decade, but github stopped enforcing their inactive account policy except for trademark violations...), picotron64/picotron-community seem like good alternatives, I can also make a converter from markdown to this json format, but I assume that kind of ruins the point of interactive editing inside Picotron, and this runs into the same staleness issues as before...

[scrapSavage]

Sorry this flew under my radar, I'll merge this so it doesn't conflict with your converter. Currently I'm a bit busy but within the next few days I think we should talk about the best way to change the formatting to allow for new behaviors since the old wiki formats were written really quickly so I could start letting people write documentation. I'll also send you an invite to the organization so that you can add your repository.

[bbb651]

No problem, I've made picotron-wiki in the meantime, I'm still working on my frontend there's no rush, I think using markdown natively inside picotron is also be a good option, it's a bit more complicated to parse but it's not that bad especially given that there are many existing lua implementations, and imo it's easier to edit than forms.
I think a way it could work is by letting you edit a single paragraph (very similar to the existing element separation) at a time (perhaps shown a pencil icon on the right when you hover over a paragraph, or in a context menu), which would render it as a text editor that let's you edit it when keeping the rest of the page above and below it rendered. This is a lot simpler from making formatted text editable, and more using friendly than having a split/toggle view, it's basically how pod gfxs behave in the text editor.