[DIP Proposal] Editor / Preview / Tag for SEO / Thumbnail
Hello Steemit community, the @upvu.witness team is back here with a NEW DIP PROPOSAL. After diligent development efforts over the past few months, we have successfully completed our first DIP mission, and now it is time to move on to the next step.
In a previous post, we mentioned items that need further development on Steemit. In order to make the delivery even a little faster, I would like to submit the second proposal as follows.
Even if you're very busy, the Steemit team(@steemitblog) and CDR(@dip.team) would appreciate it if you could quickly evaluate our proposal and give us feedback on whether it's feasible!
Cc : @steemitblog @steemcurator01 @steemcurator02 @justyy @future.witness @steemchiller @dev.supporters @smt-wherein
A. Proposal Overview
➊ Editor Feature : There is a limit to improving user experience only by providing Markdown templates. Therefore, we need to be able to provide editors provided by third-party platforms. The Editor function is a great help for general users who are not familiar with Markdown or HTML to create more well-organized content.
➋ Enable side-by-side editor & preview screen : Currently, Steemit has post previews up and down, which can be a bit inconvenient. To solve this problem, we want to provide the ability for users to change the post preview left and right at any time.
➌ Additional Tag function for SEO using metadata : Currently, Steemit's tags are limited to 5, only English is available, and tags are used to select communities. For this reason, SEO (Search Engine Optimization) is not good, so to solve this problem, we want to provide a function that allows you to enter non-English keywords using metadata.
➍ Thumbnail designation and Short description features : Unlike the current method where the first image inserted in the text automatically becomes a thumbnail image, we want to provide the ability to select a thumbnail that is exposed in the post preview. A preview summary function that can replace the first part of the post body with a short description instead of being automatically exposed in the preview.
B. Team Members
- Team Name : @upvu.witness
- Developer : @realmankwon, @happyberrysboy, @nodehub +2 more external dev(part-time)
C. Team Experience
The UPVU team members have been involved with Steem since its founding in 2016. We have been operating and optimizing Steemcoinpan (Steem side-chain based community) and UPVU service, the largest SP aggregator in Steem, for 3 years.
We are also developing and maintaining Steem keychain, a chrome extension wallet for Steemit users.
We recently developed and are operating Steempunks, the first NFT project based on the Steem blockchain, and Steemsquad, the NFT Marketplace.
We successfully completed our first DIP mission and the report is available here.
D. Request Budget & Milestone
- Request Budget : 15,300 USD
- Estimated Duration : 9 weeks
| Number | Deliverable | Specification |
|---|---|---|
| 01 | Editor Feature | - The Editor function is a great help for general users who are not familiar with Markdown or HTML to create more well-organized content |
| 02 | Side-by-side Editor & Preview | - Provide the ability for users to change the post preview left and right at any time |
| 03 | Additional Tags for SEO | - provide a function that allows you to enter non-English keywords using metadata |
| 04 | Thumbnail & Description | - provide the ability to select a thumbnail that is exposed in the post preview |
Common tasks of deliverable above
- Check component codes, file and folder structure
- Implement the code changes following the conventions of the project
- Post-changes software compatibility testing
- Reviews, corrections, final tests, pull request
Further planning for the next DIP
While developing the Steem DIP as the first runner, it was found that there are still many areas that need additional development to improve the user experience and completeness of Steemit.
(I am not sure if it will be possible to proceed with the next DIP proposal), but the items I would like to propose as the next DIP item are as follows.
➊ Editor feature
- There is a limit to improving user experience only by providing Markdown templates. Therefore, we need to be able to provide editors provided by third-party platforms.
- The Editor function is a great help for general users who are not familiar with Markdown or HTML to create more well-organized content.
➋ Enable side-by-side editor & preview screen
- Currently, Steemit has post previews up and down, which can be a bit inconvenient.
- To solve this problem, we want to provide the ability for users to change the post preview left and right at any time.
➌ Additional Tag function for SEO using metadata
- Currently, Steemit's tags are limited to 5, only English is available, and tags are used to select communities
- For this reason, SEO (Search Engine Optimization) is not good, so to solve this problem, we want to provide a function that allows you to enter non-English keywords using metadata.
➍ Thumbnail designation and Short description features
- (Thumbnail designation) Unlike the current method where the first image inserted in the text automatically becomes a thumbnail image, we want to provide the ability to select a thumbnail that is exposed in the post preview.
- (Short description) A preview summary function that can replace the first part of the post body with a short description instead of being automatically exposed in the preview.
[the 1st Steem DIP proposal related posts]
We will begin development as soon as this proposal is accepted. We ask for the support and Resteem of the community members so that we can deliver the product even a little faster. thank you!
Best Regards,
UPVU witness team
One of the original stated goals of DIP was to broaden the base of developers supporting the chain. Giving the upvu team a second bite at the apple before smaller or less established teams have had even a single chance seems actively counterproductive to that goal.
I see no reason these ideas need to be linked in a unified proposal, why not split them up as several different community proposals?
I don't understand what is being proposed here. If third party platforms provide editors can't they just spit out markdown code that users can then paste into the steemit UI? What sort of integration is being proposed here?
I think you should explain in more depth what is "not good" about this, why it matters, and whether you have ideas for how to measure the improvement you expect your proposal to cause.
This seems like a good idea that could improve the experience of a lot of users. It also seems like it ought to also be pretty self-contained. It would make sense to me for DIP funds to be allocated for this, but it also seems like a good proposal to use in support of the goal of incubating new or not-already-established teams.
Thank you for your nice comments @danmaruschak. To be clear, we really do want other teams to actively participate in DIPs besides our team or the external developer group (@nodehub) we're trying to bring to the Steem ecosystem. We do not know if the 2nd DIP proposal will be accepted just because we raised it, we just hope that steady improvement efforts will continue in the Steem ecosystem.
Steem DIP is a meaningful initiative program that the @steemitblog team is attempting for the first time to develop the ecosystem, and Steemians with development skills must have a high participation rate so that the program can proceed steadily next year. We will gladly accept the outcome of any other DIP proposal submission team, even if our proposal is subordinated or even not accepted.
From what I know, @danmaruschak you are also a good developer, with good insights and a lot of active experience on Steem. Why don't you submit a proposal and contribute to the Steem DIP's high participation rate? If your proposal is posted, I would like to actively support it!
I wasn't confident in my ability to scope and budget things so I didn't submit any fully-formed proposals, but I did submit a few ideas as community proposals, eg here and here. The way I thought things were going to work was that the @dip.team was going to review community proposals and do the scoping aspect and then invite developers to pitch to work on them. I thought I might put myself forward at that stage, but the part where community proposals got reviewed hasn't happened (yet?).