Website content strategy
In this discussion I want to brainstorm on the structure of the website. The current draft of Social Coding is just an idea.
- Crowdsourced. The site is edited collectively. Content is added all the time.
- Extensible. Site hierarchy must support addition of pages and sections without becoming cluttered.
- Intuitive. Nagivation paths must be clear and obvious, using cross-refs, ToC's, etc.
- Inviting. Explaining concepts well, showing where improvements are needed, asking for contribution.
Current draft has the idea to expose the following elements:
- Home: A summary, explanation and drill-down to various site sections.
- Principles: Principles & values of Social Coding clearly explained.
- Challenges: Top-level section that lists a growing number of FOSS's common challenges.
- [A Challenge]: An analysis of a particular challenge with in-depth elaboration.
- Solutions: Particular solutions we explore in Social Coding and challenges they address.
- Practitioners guide: Recommended process, a handbook for the FOSS development lifecycle.
- Best-practices: A pattern library, knowledge base of common patterns & practices that work.
- [A Best-practice]: A recipe to mitigate or solve particular challenges.
- IdeationHub: Sub-project for supportive tools that wield the fediverse, dogfood social coding.
In the site content list above there are 2 and maybe 3 page types that are derived from a template:
- Challenge template
- Best-practice template
- Solution template (maybe)
These templates have a fixed section layout so it become easier to read them. Think similar to the famous OOP design patterns.
Initially there can be a single Solutions page that matches challenges with ways to address them. Once this grows too long it can become a top-level page with individual solutions elaborated below.
Deleting a branch is permanent. It CANNOT be undone. Continue?