louiscklaw/004_comission
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
c27c975273e1f558bc57ab76d74fd2bb804019c7
004_comission/amicho/promptbase.com-clone/prompt-base-technical-proposal/rpompt-base-technical-proposal.md
louiscklaw ad92aa80a9 update,
2025-01-31 19:24:26 +08:00

3.8 KiB
Raw Blame History 

對唔住，我望望下就算 POC 都好
單靠 wordpress 都未必 handle 得到 
(我意思指可能要另外租機 / 租hosting 去做)

我嘗試一下輕度 drill down 多小小再搵搵你
今日星期五，報價/報期方面
最遲你預我星期一好嘛，星期一 一定有答案，
我會盡快做

用呢個機會 align 一下 requirement:
  - https://promptbase.com
  - member system
  - selling prompt

不如我先回答一下個報價方向，
其實好似呢類型 website ，因為佢地頁同頁之間有 logic 連住
而個 logic 唔似之前 clone 網頁咁可以好簡單咁去摸底。

因為 logic 冇得摸底，所以報價的話會偏向報工日
(我會首先收一個價錢出一個 draft/clone ，之後對個 draft/clone 有要求的話可以提出，
做一日收一日錢，又或者做一個 feature 收一個 feature 錢
但係有陣時有D 功能/fix/feature 要一兩個星期完成)

老實講，髒話說在前面。
雖然我做一日收一日錢，咁我會盡力去減少 bug 嘅出現/重覆出現，
但係我冇可能保證成件事係 bugs free / 出現過嘅 bug 永遠唔再出現.

(對上面嘅文字有任何疑問歡迎聯絡我)

technical/implementation proposal

outline

  • promptbase.com is a marketplace:
    • to sell prompts that's able to feed into various AI model
      • prompt engineers can sell their crafted instructions for image-generation tools such as Midjourney
    • to sell talent helping people to design prompt

AI prompt covered:

current contents of promptbase.com

  • member system
  • prompt gallery
  • shopping cart / stripe / online payment
  • marketplace
    • Best AI Prompts
    • Best Midjourney Prompts
    • Best GPT Prompts
    • Best DALL-E Prompts
    • Best Stable Diffusion Prompts
  • various page
    • FAQ
    • Contact
    • chagne log
    • Blog
    • Privacy

implementation:

As currently promptbase mainly consists of two parts:

  • CMS related
    • FAQ
    • Contact
    • Changelog
    • Blog
    • Privacy
  • non-CMS related / dynamically generated
    • marketplace
    • shopping cart / stripe
    • member system
    • hire (talent market)
    • gallery

Therefore, various system will be involved:

  • CMS realted will be catered by wordpress
  • non-CMS part will be catered by laravel.

As various system involved. A private/virtual PC hosting is suggested (i.e. google cloud).

The statement above is so call a high level design. Some detail (i.e. reverse proxy, object stoage, self-owned stable diff) were not stated above. However, they will be employed if necessary. More ad-hoc computing resources may be required.

implementation

The proposed development cycle will be as follow:

  • collect requirements (variable)

    • assign priority / divide concept pieces

  • development ignition (6 weeks)

    • CMS part integrate (wordpress)
    • non-CMS related part
      • gallery
      • member system

  • receive comments / back-and-forth (1~2 week cycling)

  • phrase in stripe (3~4 weeks)

  • administrator panel (5 weeks)

Subject to requirements may be change. Some roles/components may not mentioned above. So, the project schedule may be changed/re-propose when required.

references / slimiaries / competitors