ComputerScienceHouse / ComputerScienceHouse/conditional
Proposal: Richer project descriptions
- 主要语言
- Python
- 星标
- 12
- 派生
- 39
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 1
描述
Just going to toss out an idea myself and others have been kicking around for a few years that I'd really like to see implemented.
It would be nice to take advantage of the fact we require descriptions of projects for submission to eboard for PR/record keeping purposes. Concretely, I'd like the following functionality (and happy to implement myself):
- [ ] project descriptions may include some form of richer text, preferably markdown or something similar, possibly user choice.
- [ ] Images and other attachments (but hopefully not malicious code) may be attached.
- [ ] Projects must be marked as published in some fashion. Ideally anything that is a major project should be worth bragging about.
- [ ] Public facing project blog should be exposed, attributing contributions to project authors, this should either be linked to by the main site or incorporated.
贡献指南
这个仓库没有索引到贡献指南
调研方向
未指定文件、测试或入口点。首先定位现有的项目提交和描述流程,然后确定富文本、附件、发布状态和项目博客将如何结合。完成的标准是制定出一份已确定且范围明确的实现计划,涵盖这些要求及其安全影响。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- flask, markdown, python
- 领域
- backend, content, web-dev
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100