elixirtw / elixir_tw Goto Github PK

Ruby x Elixir Conf 2018 需要一個新的 landing page，一個稍微正式一點的。
歡迎對於 design 有心得的朋友來投稿喔!

• 使用者登入
  我原本想說可以用 username + password + 多個Oauth (github, facebook), 不過UI 的 flow 上會比較繁瑣，所以先只用好FB登入 (可以很快地換到 github)。
  • Username + Password + reCAPTCHA
  • Facebook Oauth
  • Github Oauth
  • 使用者可以顯示 Gravatar or Default Logo
• 發文
  • 使用者可以發文
  • 文章有 slug
  • 文章有 Excerpt，可以自定義或是 Excerpt 擷取 body前 150 個字元
  • 文章可以由Admin 置頂
  • 文章用Markdown編輯
  • 從圖片url load 圖片
  • 可以預覽文章
  • 文章有Tag
  • Tags 為系統預定 (Announcements, Jobs, Tutorials ... 其他再想想，大概四五個就好)
  • Maybe Emoji?
• 回文
  • 或許可以直接用Post 來存，利用類似 commented_id + position 來存對應的回文。
  • 回文一樣適用 Markdown 來編輯
• 版面
  • Landing Page
  • 顯示所有的Post
  • 每個 Tag 都有對應的 Tabs 可以切換過去，只顯示有那個 Tag 的 Posts
  • 一次只顯示N個 Posts (Pagination)
  • 閱讀文章的頁面
  • 文章能夠Comment
• OPs
  • 找地方 Host (Digital Ocean)
  • deployment
  • 加入 Google Analytics
  • https
  • license

我覺得 Post 因該不用 validate_required(:title)
一來是因為已經有 slug 來判斷是哪篇文章，另外或許使用者可以比較自由的選擇要不要使用 Title
沒有的就只是 SEO 對他們比較不利 + 看起來比較醜~
@taiansu

哈摟 @henry40408

下一版的 Brunch (2.10) 才有支援才有支援 Yarn. 😞

id -> user_id, Column types are different in the primary and foreign table.
user_id of posts table should be bigint.

User Table

CREATE TABLE public.users (
    id bigint NOT NULL,
    name character varying(255),
    email character varying(255),
    crypted_password character varying(255),
    inserted_at timestamp without time zone NOT NULL,
    updated_at timestamp without time zone NOT NULL
);

Posts Table

CREATE TABLE public.posts (
    id bigint NOT NULL,
    title character varying(255),
    slug character varying(255),
    body text,
    user_id integer NOT NULL,
    inserted_at timestamp without time zone NOT NULL,
    updated_at timestamp without time zone NOT NULL,
    pinned boolean DEFAULT false,
    markdown_body text
);

嗨 @otaq
我看到你一個月之前有做一個 yarn branch

有需要什麼協助嗎? =)

Hi @yuchunc, I'm new to Elixir Taiwan.

I saw 9529e6f that whole semantic-ui source code was committed. It's quite huge for a git commit and icon fonts and css flag sprites are not working.

IMHO we shouldn't commit dependency's source code into repo, since we don't want to maintain or customize it or do we? Actually if we want to customize a dependency, we should fork it as our customized dependency repo, not commit it into project repo. Follow this idea, in this case, the only thing we do to semantic-ui is manage its version.

Here is my minimal configuration for semantic-ui otaq/elixir_tw@813a8c638fd40deb074d2afc43691cfaf26e7165 icon fonts and css flag sprites are working.

I can create a pull request with these commits if you like or just close this issue. Although I wish to remove semantic-ui source code entirely from git history, use git rebase -i and git push -f just for this case but I don't have permission. Any ideas?