內容簡介
Awesome Portfolio 是一個非常現代和傑出的 Mixitup 作品集，可以使用平滑的動畫和酷炫的圖像懸停效果過濾。從眾多效果和動畫預設中選擇，以自定義作品集的外觀。只需幾分鐘便可設置、自定義和發布作品集。
短碼為：[awesome-portfolio]
上面的幾點說明：
"貢獻者"是一個用逗號分隔的 WordPress.org 用戶名列表
"標籤"是一個用逗號分隔的適用於外掛的標籤列表
"至少需要"是該外掛可運行的最低版本
"測試至"是您已成功測試該外掛的最高版本。請注意，它可能在更高版本上運行...這只是您驗證過的最高版本。
穩定版應該指定最新穩定版本的 Subversion "標籤"，如果您使用 /trunk/ 作為穩定版本，則為 "trunk"。
請注意，穩定標籤的 readme.txt 是被認為是定義外掛的文件，因此，如果 /trunk/readme.txt 文件指出穩定標籤是 4.3，則它是 /tags/4.3/readme.txt，這將被用於顯示有關外掛的信息。在這種情況下，從樹幹 readme.txt 中考慮的唯一事項是穩定標籤指針。因此，如果您在樹幹中開發，則可以更新樹幹 readme.txt 以反映正在開發版本中的更改，而不會將有關那些缺少這些更改的當前穩定版本的信息錯誤地披露 - 只要樹幹的 readme.txt 指向正確的穩定標籤。
如果沒有提供穩定標籤，則假定樹幹是穩定的，但如果您將穩定版本放在樹幹中，則應指定 "trunk"，以消除任何疑慮。
任意節點
您可以提供與上面相同格式的任意節點。這對於需要傳達更多信息但不符合“描述”或“安裝”的類別的極其複雜的外掛非常有用。任意節點將顯示在上面概述的內置節點下面。
簡短的 Markdown 示例
有序列表：
某些功能
另一個功能
關於外掛的其他內容
無序列表：
某物
其他東西
第三個東西
這裡是連結到WordPress和Markdown的語法文檔的鏈接。標題是可選的。
Markdown使用電子郵件風格的註釋區塊引用，並且我已經被告知：
使用星號進行強調。把它加倍強調。
<？php code(); //用於標識代碼的反引號?>
外掛標籤
開發者團隊
原文外掛簡介
Awesome Portfolio a very modern and outstanding Mixitup portfolio that can be filtered using smooth animations and cool image hover effects. Select from a huge set of effects and animation presets to customize the look of your portfolio. Set up, customize and publish your portfolio within just a few minutes.
shortcode is :[awesome-portfolio]
A few notes about the sections above:
“Contributors” is a comma separated list of wordpress.org usernames
“Tags” is a comma separated list of tags that apply to the plugin
“Requires at least” is the lowest version that the plugin will work on
“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on
higher versions… this is just the highest one you’ve verified.
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for
stable.
Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so
if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that’ll be used
for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in
your in-development version, without having that information incorrectly disclosed about the current stable version
that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where
you put the stable version, in order to eliminate any doubt.
Arbitrary section
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
A brief Markdown Example
Ordered list:
Some feature
Another feature
Something else about the plugin
Unordered list:
something
something else
third thing
Here’s a link to WordPress and one to Markdown’s Syntax Documentation.
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
Asterisks for emphasis. Double it up for strong.
