A test feture story #3
Labels
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Depends on
#2 the current tools are programming first, we need to change this to editoral process first
indymedia/Editorial-Collective
Reference: indymedia/Editorial-Collective#3
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
the draft is here https://unite.openworlds.info/indymedia/Editorial-Collective/wiki/a-test-front-page-story
OK this is not the best as the list of pages on the wiki will become to long to soon. ideas for storeing the story drafts.
what process are you aiming for? would this for actual publication?
To have one wiki page per "article"?
Then yeah, I imagine it gets tricky with hundreds of articles.
You would probably need something more like a blog.
https://gohugo.io would be great option for that.
i imagine gitea and the wiki is more for sorting and organising process rather than content?
Nice to have it all in one places - the is the option of linking out to a another wiki platform for the content which can handle the number of pages with a better UI.
The newswire is all user generated mostly by posting on other activertypub sites and aggregating in with tags (trusted by tag and source etc)
The features are less numerous and a wiki is a good place to wright them as they are collectively produced by a group based on the newswire story sources.
A nice structured wiki is perfect for this #4opens Thinking now we can just use the built in one to start then think about scaling latter.
You guys should find some sources explaining
how indymedia worked :)
I don't mean to be rude.. but might help, a markdown tutorial :)