FAQ Center :: Home All
7 Workflow & Content Management - Advanced
- Why is TortoiseGit recommended for site management? —> Non-Technical Leads, Content Authors
- How often should content commits be pushed to Git? —> Authors, Content Managers
- What happens if a bad commit is pushed to the server? —> Site Administrators
- Can multiple team members work on the same site simultaneously? —> Team Leads, Collaborators
- How are raw text files structured for long-term digital preservation? —> Archivists, Data Stewards
- How do I organize a multi-tier folder structure for a large site? —> Information Architects, Content Leads
- Can I publish draft articles without showing them in the main menu? —> Authors, Editors
- How do I integrate custom presentation slides alongside blog posts? —> Presenters, Educators
- What is the best way to manage legacy PDF document archives? —> Archivists, Librarians
- How do I maintain consistency across long-term content updates? —> Editors, Project Leads
Group: Version Control & Git
Question: Why is TortoiseGit recommended for site management?
Applies To: Non-Technical Leads, Content Authors
Answer: TortoiseGit integrates directly into Windows File Explorer, providing visual status icons, easy right-click commits, and intuitive diff checks.
Context: Lowers the technical barrier for non-developers learning version control workflows.
Group: Version Control & Git
Question: How often should content commits be pushed to Git?
Applies To: Authors, Content Managers
Answer: Commits should be made whenever a logical piece of work is completed, creating clean restore points before deployment.
Context: Promotes disciplined file management and clear activity tracking over time.
Group: Version Control & Git
Question: What happens if a bad commit is pushed to the server?
Applies To: Site Administrators
Answer: You can simply revert to the previous working commit locally using Git and re-upload the restored files via FTP.
Context: Makes site recovery simple, fast, and stress-free.
Group: Version Control & Git
Question: Can multiple team members work on the same site simultaneously?
Applies To: Team Leads, Collaborators
Answer: Yes. Standard Git branch and merge workflows allow multiple collaborators to work offline and integrate changes cleanly.
Context: Enables seamless team collaboration without risking live server content overwrites.
Group: Version Control & Git
Question: How are raw text files structured for long-term digital preservation?
Applies To: Archivists, Data Stewards
Answer: Files use open, standard UTF-8 plain text with minimal formatting tags, ensuring readability across any future computing platform.
Context: Guarantees that content remains accessible decades after specific software frameworks disappear.
Group: Content Strategy
Question: How do I organize a multi-tier folder structure for a large site?
Applies To: Information Architects, Content Leads
Answer: Group content into clear top-level categories, use node folders for major topics, and sub-node folders for specific subtopics or series.
Context: Translates complex organizational taxonomies into intuitive desktop folder trees.
Group: Content Strategy
Question: Can I publish draft articles without showing them in the main menu?
Applies To: Authors, Editors
Answer: Yes. Placing files outside active node folders or excluding them from index sheets lets you share direct page URLs confidentially.
Context: Allows offline drafting, review, and selective sharing before public site inclusion.
Group: Content Strategy
Question: How do I integrate custom presentation slides alongside blog posts?
Applies To: Presenters, Educators
Answer: Store RevealJS slide files within their own node subfolder, linking them directly from related article pages or index menus.
Context: Combines long-form written content with interactive slide presentations under one unified roof.
Group: Content Strategy
Question: What is the best way to manage legacy PDF document archives?
Applies To: Archivists, Librarians
Answer: Upload legacy PDFs to the CDN subdomain and link to them from descriptive HTML index pages for fast, responsive browsing.
Context: Keeps raw repositories lightweight while making legacy PDF documents easy to access.
Group: Content Strategy
Question: How do I maintain consistency across long-term content updates?
Applies To: Editors, Project Leads
Answer: Follow your 3-year content outline, review local diffs before publishing, and adhere to standardized page metadata headers.
Context: Maintains structural discipline and high quality across multi-year publishing projects.