Publishing The Neopolitan Files

Kicking around the idea that Neopoligen should publish the underlying Neopolitan files along with the web page.

This would do two things:

Provide a what I think would make a solid accessability resource.
Provide part of the foundation for a social network. e.g. folks could pull individual posts and process them as part of their like/bookmarks/replys etc..

There's one key here which is making sure (as much as possible) that folks know that anything they write will go out in these files. That won't be surprising for the most part since they're designed for publishing, but the one place it may catch folks is with any type of "comment" functionality where what you write in the Neopolitan file is skipped during output.

I built comments into earlier versions of Neopoligen, but I'm now planning to not do that for version 42 (which is what I'm planning to launch).

That way there's no confusion or mental overhead. The stuff you write in the file goes out, period.

Other Thoughts

Yeah, it's totally possible to build a custom comment functionality into your own instance, but I'm not planning on adding a feature to edit the .neo files in flight to remove it from the source.
There could be a switch to turn off the .neo files, but that doesn't seem like it's worth the effort. The content would be published regardless. It would just make getting to it a little harder.
One potential negative side effect is with any images who use metadate for their alt text. That alt text wouldn't be in the .neo file becuase the entire point is that you house it with the image itself. I'm thinking that if an image has built in alt text we output a .neo file beside the image with the text in it. That would let folks access it that way. (would take a jump, but it's a start at least, I think)

-- end of line --