Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project/Content Organization #11

Closed
iheartcryptocoin opened this issue Mar 15, 2014 · 6 comments
Closed

Project/Content Organization #11

iheartcryptocoin opened this issue Mar 15, 2014 · 6 comments
Labels
Milestone

Comments

@iheartcryptocoin
Copy link
Contributor

The information in Docs, Resources, and Get Peercoin is redundant and disorganized abd references information that is off site

I propose we organize into 3 Sections

Understand Peercoin
-About Peercoin
-About Mining
-About Minting
-About Spending

Use Peercoin
-Mining Tutorial
-Minting Tutorial
-Spending/Accepting Tutorial-
Other Tools Tutorial

Peercoin Community
-Overview/How to get started
-Understanding Forums
-Peercoin on Social Media (covers best way to contact folks for help)
-Volunteer
-Sponsor/Donate

This would require merging texts across several of the current pages and continuing to pull in information that was only contained on forum as was done for the news and events page

@super3
Copy link
Owner

super3 commented Mar 15, 2014

ACK, on the concept. Here are my changes.

Learn

  • About Peercoin
  • Whitepaper
  • Mining + Tutorial
  • Minting + Tutorial

Use Peercoin

  • Trade Listings

Community

  • Overview/How to get started
  • Social Media (covers best way to contact folks for help)
  • Volunteer
  • Sponsor/Donate

Forum

@iheartcryptocoin
Copy link
Contributor Author

Before continuing let's lay out some audience principles.

Specifically what is the site audience and how much previous knowledge do we assume the audience will have? What audience do we want to ignore?

If the site is designed for general public with very little knowledge then, site needs to be gateway for both technical and non-technical people to understand cryptos at the conceptual level, and peercoin specifically. This will require having fairly complete "about sections" available.

We wwould also need to provide technical information to empower that general audience and also deeper technical info for people already involved in the crypto world.

The wiki project is probably a reasonable place to warehouse all of the deeper technical specifications/tutorials. HOWEVER we could also include and "advanced user" area on the site with a series of articles if we are seeking to serve that audience here if we want to serve them

We need to decide on the audience and that will make the organization clearer.

For example, In addition to what you propose above, a beginner/ less technical general audience also need (not exhaustive list)

  • Spending/Accepting/transactions Tutorial
    and
  • other tools tutorials (block chain explorer, mining profitability calculator , intro to price charting etc)
  • and so fourth

If we don't want to serve this audience, then we need not include this. This is good work, once we have this decided and the organization laid, out producing and organizing content will go much faster

We'll also need to decide on Some editing conventions (ie US vs euro spelling) but that is a conversation for after the core content is decided

@super3
Copy link
Owner

super3 commented Mar 15, 2014

I say split the website into various subsites, each with their own goals. Trying to manage the thing as a whole leads to much confusion.

@iheartcryptocoin
Copy link
Contributor Author

Yup. How about 3 areas

MAIN - peercoin.net as the general interest page
High level overview of the coin
track news and events
press kit material
contact us information
list of sponsors
sign up to volunteer

SUB 1 tutorials.peercoin.net or knowledge.peercoin.net or something similar for
articles/knowledge base split into 3 levels

  • Beginner(downloading the wallet getting started mining and minting etc)
  • Intermediate(dealing with exchanges, more complex transactions like multi sig, using command line, etc)
  • Advanced (how to start coding with the api, information about coding projects etc etc etc)

SUB 2 commerce.peercoin.net
tutorialsreviews/listings etc for
localpeercoins
exchanges
payment processors
Merchants
etc

@iheartcryptocoin
Copy link
Contributor Author

We should organize the project management process. This is especially important so that we can also split content generation from content deployment to keep things organized/less confused.

For different article editing we can establish new gits
Each article text is stored on a page and folks can contribute edits etc.

Once articles are finalized we then move to website and mark up. No more edits or changes without good cause.

Appoint 2 or 3 editors to manage this process

List each set of articles as a P4C project and split the current P4C funds across the different articles that need to be written/edited to reward writers

thoughts??

3 Team Roles

  1. Back end guys - build/deploy very simple CMS and skeleton of site organized for the different articles that will be posted. Make updates as content needs change

  2. Editors oversee Writing projects -> writers contribute to drafts via pull until finalized

  3. Technical Markup guys - Take finalized article text and mark up for posting to site, pull reqs to main repo

Folks would prob participate in 2 of 3 team roles at any given time. Some writers might help with mark-up, some mark-up folks prob help with back end. etc

@super3 super3 added this to the Design Issues milestone Mar 21, 2014
@super3 super3 added the content label Mar 21, 2014
@super3
Copy link
Owner

super3 commented Mar 21, 2014

Yes, I think that is definitely a route to go. I think first we need to focus on taking a bit of time to clean up the current website(simply because we can do that now and quickly), then transition to something like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants